dbcve.org
Quiz MakerWordPress extension · Ays Pro

CVE-2025-10042

HIGH · 7.5 CVSS v3.1 Published 2025-09-17
Fix available
A fix is available. Upgrade to 6.7.0.57 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 SQL Injection via spoofed IP headers in all versions up to, and including, 6.7.0.56 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable in configurations where the server is set up to retrieve the IP from a user-supplied field like `X-Forwarded-For` and limit users by IP is enabled.

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 fails to properly sanitize IP addresses retrieved from HTTP headers (X-Forwarded-For) before using them in SQL queries. When the 'limit users by IP' feature is enabled and the server is configured to trust user-supplied IP headers, unauthenticated attackers can inject arbitrary SQL commands by spoofing these headers, potentially exfiltrating sensitive database contents.

MitigationDisable the 'limit users by IP' feature in the plugin settings immediately. Update to version 6.7.0.57 or later when available, and configure the server to only trust trusted proxy headers rather than arbitrary user-supplied values.

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

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 the installed Quiz Maker plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Quiz Maker' or check the plugin's main PHP file for the version comment/constant. Alternatively, check the file: /wp-content/plugins/ays-quiz-maker/readme.txt for the 'Stable tag' entry.
    Affected if The version listed is lower than 6.7.0.57 or the stable tag shows a version below 6.7.0.57.
  2. Locate the plugin settings for IP-based restrictions
    In WordPress admin, navigate to Quiz Maker > Settings > General (or similar) and look for options labeled 'Limit users by IP', 'IP Restriction', or 'Restrict by IP address'. These are typically found under security or user access settings.
    Affected if The 'limit users by IP' feature is enabled or set to 'Yes' in the plugin configuration.
  3. Verify server trust configuration for X-Forwarded-For headers
    Check your web server (Apache/Nginx) configuration or PHP code that processes the X-Forwarded-For header. In Apache, look for 'RemoteIPHeader X-Forwarded-For' with 'RemoteIPTrustedProxy' allowing untrusted sources. In Nginx, check for 'real_ip_header X-Forwarded-For' with 'set_real_ip_from' pointing to non-restricted ranges. Also check wp-config.php for any custom code that uses $_SERVER['X-Forwarded-For'] without validation.
    Affected if The server is configured to accept X-Forwarded-For headers from untrusted sources (such as setting RemoteIPTrustedProxy to '0.0.0.0/0' or allowing all proxies) or the application directly uses the X-Forwarded-For header without validating against a trusted proxy list.
  4. Confirm the SQL injection entry point is reachable
    The vulnerability is triggered when the 'limit users by IP' feature is active and a request includes an X-Forwarded-For header. There is no direct file or config to check; this requires understanding that any public-facing quiz page that uses the IP limit feature will process the header. Verify if any published quiz has the IP restriction option enabled in the quiz settings.
    Affected if Any quiz is published with the IP limitation/restriction feature turned on, making the SQL injection vulnerable to exploitation via crafted X-Forwarded-For headers.

You are affected if your installed Quiz Maker plugin version is below 6.7.0.57 AND the 'limit users by IP' feature is enabled on at least one quiz, AND your server trusts X-Forwarded-For headers from untrusted sources.

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.57 or later
Fixed in 6.7.0.57
Interim mitigation

Disable the 'limit users by IP' feature in the plugin settings immediately. Update to version 6.7.0.57 or later when available, and configure the server to only trust trusted proxy headers rather than arbitrary user-supplied values.

Recommended fix High confidence

6.7.0.57

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the Quiz Maker plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 6.7.0.57.
  5. 5. Alternatively, navigate to Dashboard > Updates and select Quiz Maker to update.
  6. 6. Verify the installed version shows 6.7.0.57 after the update completes.
  7. 7. Test that quiz functionality continues to work as expected.

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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