dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-6817

MEDIUM · 5.8 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Quiz Maker by AYS plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'rate_reason' parameter in all versions up to, and including, 6.7.1.29 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Quiz Maker by AYS WordPress plugin (versions up to 6.7.1.29) contains a stored XSS vulnerability in the 'rate_reason' parameter. Unauthenticated attackers can inject malicious JavaScript through insufficient input sanitization, which persists in the database and executes when users access affected pages due to missing output escaping.

MitigationUpdate the plugin to version 6.7.1.30 or later, which should include proper input sanitization (e.g., sanitize_text_field) for the 'rate_reason' parameter and output escaping (e.g., esc_html/esc_attr) when rendering user-submitted content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Quiz Maker plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Quiz Maker by AYS' in the list of active and inactive plugins
    Affected if Plugin is present in the WordPress installation
  2. Check the installed version number
    In the same Plugins screen, note the version number displayed beneath the Quiz Maker plugin name (for example, 'Version 6.7.1.29')
    Affected if Version is 6.7.1.29 or earlier
  3. Verify rate_reason functionality is exposed
    Identify if your quiz setup includes a rating or feedback form that accepts a 'rate_reason' parameter from users; this is typically found in quiz review or rating submission features
    Affected if The rate_reason input field is accessible to users (unauthenticated according to the CVE)
  4. Determine if unsanitized output is rendered
    Inspect your database for any stored rate_reason entries or view page source of quiz results to see if user-submitted rate_reason content is rendered without escaping
    Affected if User-submitted rate_reason data is stored and displayed without proper sanitization and escaping

You are affected if the Quiz Maker plugin version is 6.7.1.29 or earlier AND your quizzes process and display the rate_reason parameter from users without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 6.7.1.30 or later, which should include proper input sanitization (e.g., sanitize_text_field) for the 'rate_reason' parameter and output escaping (e.g., esc_html/esc_attr) when rendering user-submitted content.

Recommended fix Moderate confidence

Version 6.7.1.30 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Quiz Maker by AYS' in the plugin list
  4. Check if the current version is 6.7.1.29 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/quiz-maker and upload manually
  7. After updating, verify the new version number reflects the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6817 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6817 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data