dbcve.org
Quiz MakerWordPress extension · Ays Pro

CVE-2025-58015

HIGH · 7.5 CVSS v3.1 Published 2025-09-22
Fix available
A fix is available. Upgrade to after 6.7.0.61 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
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Ays Pro Quiz Maker quiz-maker allows Retrieve Embedded Sensitive Data.This issue affects Quiz Maker: from n/a through <= 6.7.0.65.

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 · moderate confidence

Ays Pro Quiz Maker plugin versions up to 6.7.0.65 contain an information disclosure vulnerability allowing unauthorized users to retrieve embedded sensitive data. This exposure of sensitive system information to an unauthorized control sphere could expose system paths, configuration details, or internal application data.

MitigationUpdate Quiz Maker to version 6.7.0.66 or later if a patch is available. Until then, restrict access to quiz-related endpoints and monitor for unauthorized access attempts to sensitive data.

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.61

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. Identify if Ays Pro Quiz Maker plugin is installed
    Check the WordPress plugins directory for 'ays-quiz-maker' folder, or look for the plugin in the WordPress admin under Plugins
    Affected if Plugin folder 'ays-quiz-maker' exists in wp-content/plugins
  2. Determine the installed version of Ays Pro Quiz Maker
    Open the main plugin file (usually ays-quiz-maker.php) and look for the 'Version' header in the plugin comments, or check the readme.txt file
    Affected if Version listed is 6.7.0.61 or lower
  3. Identify quiz-related endpoints
    Check for publicly accessible quiz URLs in your WordPress installation, typically under /quiz/ or /ays-quiz/ paths in the wp-content/uploads/ays-quiz directory
    Affected if Quiz endpoints are accessible without requiring authentication
  4. Test for unauthorized sensitive data retrieval
    Attempt to access quiz export, results, or settings endpoints without logging in (e.g., check for AJAX endpoints in wp-admin/admin-ajax.php related to the quiz maker or direct file access)
    Affected if Sensitive system information, file paths, or configuration data is returned without authentication

You are affected if Ays Pro Quiz Maker plugin is installed with version 6.7.0.61 or lower and quiz-related endpoints are accessible to unauthenticated users.

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 a release after 6.7.0.61
Interim mitigation

Update Quiz Maker to version 6.7.0.66 or later if a patch is available. Until then, restrict access to quiz-related endpoints and monitor for unauthorized access attempts to sensitive data.

Recommended fix Moderate confidence

Quiz Maker 6.7.0.66 or later (latest available version)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Quiz Maker plugin (by Ays Pro)
  4. 4. Check if an update is available and update to the latest version
  5. 5. Verify the update was successful by checking the plugin version

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

Fix this in Quiz Maker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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