CVE-2026-6817
Stored XSS in Quiz Maker by AYS WordPress Plugin
Publication date: 2026-05-02
Last updated on: 2026-05-05
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ays | quiz_maker | to 6.7.1.29 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Quiz Maker by AYS plugin for WordPress has a vulnerability known as Stored Cross-Site Scripting (XSS) in the 'rate_reason' parameter. This occurs because the plugin does not properly sanitize or escape input and output data. As a result, an attacker who is not authenticated can inject malicious web scripts into pages. These scripts will then execute whenever any user accesses the affected page.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary scripts in the context of users visiting the affected pages. This can lead to theft of user data, session hijacking, or other malicious actions performed on behalf of the user without their consent. Since the attack can be performed by unauthenticated users, it increases the risk of exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to inject arbitrary web scripts via stored cross-site scripting (XSS) in the Quiz Maker by AYS plugin for WordPress. This can lead to unauthorized actions or data exposure when users access the injected pages.
Such vulnerabilities can impact compliance with standards like GDPR and HIPAA because they may lead to unauthorized access or exposure of personal or sensitive data, violating data protection and privacy requirements.
However, the provided information does not explicitly detail the direct compliance implications or specific regulatory impacts of this vulnerability.