dbcve.org
Quiz MakerWordPress extension · Ays Pro

CVE-2025-12426

HIGH · 7.5 CVSS v3.1 Published 2025-11-19
Fix available
A fix is available. Upgrade to 6.7.0.81 or later.
See remediation →
84/100
Remediation priority · High
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 plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 6.7.0.80. This is due to the plugin exposing quiz answers through the ays_quiz_check_answer AJAX action without proper authorization checks. The endpoint only validates a nonce, but that same nonce is publicly available to all site visitors via the quiz_maker_ajax_public localized script data. This makes it possible for unauthenticated attackers to extract sensitive data including quiz answers for any quiz question.

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 WordPress plugin exposes quiz answers through the ays_quiz_check_answer AJAX action. The endpoint only validates a nonce that is publicly accessible via the quiz_maker_ajax_public localized script data, allowing unauthenticated attackers to extract answers for any quiz question.

MitigationUpdate to a patched version of the Quiz Maker plugin that implements proper authorization checks on the AJAX endpoint, or restrict access at the server level until a patch is available.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Quiz MakerWordPress extension
Affected:< 6.7.0.81

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 WordPress installation
    Check for the presence of wp-config.php in the web root and examine the site structure for WordPress markers.
    Affected if The site is not running WordPress - this CVE does not apply.
  2. Verify Quiz Maker plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the 'quiz-maker' folder, or query the wp_plugins database table.
    Affected if The Quiz Maker plugin is not installed - this CVE does not apply.
  3. Check installed Quiz Maker version
    Read the main plugin file (e.g., quiz-maker.php) header for the 'Version' value, or query the wp_options table for the 'ays_quiz_maker_version' option.
    Affected if The installed version is lower than 6.7.0.81 - the plugin is potentially affected.
  4. Verify the vulnerable AJAX endpoint is exposed
    Inspect page source of a quiz page for the 'ays_quiz_check_answer' action in the ajaxurl call, or manually request the endpoint at wp-admin/admin-ajax.php with action=ays_quiz_check_answer.
    Affected if The AJAX endpoint responds and accepts the request - the vulnerability is present.
  5. Confirm nonce is exposed in public script data
    View the HTML source of a public quiz page and search for 'quiz_maker_ajax_public' - the nonce will be visible in the localized script data.
    Affected if The nonce is visible in public-facing script data - authentication is bypassed and answers can be extracted.
  6. Test answer extraction capability
    Submit a request to the AJAX endpoint with a quiz ID and question ID to see if answers are returned without authentication.
    Affected if Answers are returned without requiring authentication - the environment is confirmed affected.

The environment is affected if Quiz Maker plugin version is below 6.7.0.81 and the ays_quiz_check_answer AJAX endpoint is accessible without authentication, exposing quiz answers in the response.

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
Upgrade available Upgrade to 6.7.0.81 or later
Fixed in 6.7.0.81
Interim mitigation

Update to a patched version of the Quiz Maker plugin that implements proper authorization checks on the AJAX endpoint, or restrict access at the server level until a patch is available.

Recommended fix High confidence

Quiz Maker 6.7.0.81

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Quiz Maker in the plugin list
  4. If an update is available, click 'Update Now'
  5. Alternatively, navigate to Dashboard > Updates and update Quiz Maker
  6. After update, verify the version is 6.7.0.81 or higher

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

Fix this in Quiz Maker 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 the upgrade done

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-2025-12426 — 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-2025-12426 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