dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-10493

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 Chained Quiz plugin for WordPress is vulnerable to Insecure Direct Object Reference in version 1.3.4 and below via the quiz submission and completion mechanisms due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to hijack and modify other users' quiz attempts by manipulating the chained_completion_id cookie value, allowing them to alter quiz answers, scores, and results of any user. The vulnerability was partially patched in versions 1.3.4 and 1.3.5.

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 Chained Quiz WordPress plugin versions 1.3.4 and below contains an Insecure Direct Object Reference vulnerability in the quiz submission and completion mechanisms. Due to missing validation on the user-controlled chained_completion_id cookie value, unauthenticated attackers can hijack other users' quiz attempts and modify their answers, scores, and results.

MitigationUpdate the Chained Quiz plugin to version 1.3.5 or later which includes partial patching. Verify that proper validation on the chained_completion_id is enforced to prevent unauthorized access to other users' quiz data.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify Chained Quiz plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'chained-quiz' or 'chained-quiz-quiz' and confirm its presence in the plugins list via WordPress admin or database.
    Affected if The Chained Quiz plugin folder exists in the WordPress installation.
  2. Identify installed plugin version
    Open the main plugin file (e.g., chained-quiz.php) and locate the Version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The reported version is 1.3.4 or lower.
  3. Confirm quiz functionality is active
    Check the WordPress database for published quiz entries in the wp_chained_quiz table, or log into WordPress admin and verify that quizzes have been created and are publicly accessible.
    Affected if Active quizzes exist and accept submissions from users.
  4. Inspect cookie handling for chained_completion_id
    Submit a test quiz attempt and examine the HTTP response headers and browser cookies to verify a cookie named 'chained_completion_id' is being set without proper user binding validation.
    Affected if The chained_completion_id cookie is set and can be manipulated to reference other users' completion IDs.
  5. Verify authorization on quiz completion endpoint
    Test the quiz completion API endpoint (typically wp-admin/admin-ajax.php or a frontend endpoint) by submitting requests with modified chained_completion_id values to see if the application validates ownership before allowing answer or score modifications.
    Affected if The endpoint accepts and processes requests with arbitrary chained_completion_id values without verifying the current user owns that completion record.

A user is affected if the Chained Quiz plugin version is 1.3.4 or lower and active quizzes exist that set the chained_completion_id cookie without proper ownership validation.

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 Chained Quiz plugin to version 1.3.5 or later which includes partial patching. Verify that proper validation on the chained_completion_id is enforced to prevent unauthorized access to other users' quiz data.

Recommended fix Moderate confidence

Upgrade to the latest version of Chained Quiz plugin (1.3.5 or later if available)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Chained Quiz' plugin
  4. Check the current installed version
  5. If the installed version is 1.3.4 or below, update to the latest available version
  6. After updating, verify the plugin version shows the updated release
  7. Test quiz submission and completion to ensure functionality works correctly
  8. Consider reviewing the chained_completion_id cookie handling if custom configurations exist

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10493 — 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-10493 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