dbcve.org
WpquizWordPress extension · Bauc

CVE-2025-6739

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to after 0.4.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 WPQuiz plugin for WordPress is vulnerable to SQL Injection via the 'id' attribute of the 'wpquiz' shortcode in all versions up to, and including, 0.4.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 WPQuiz WordPress plugin has a SQL Injection vulnerability in the 'wpquiz' shortcode handler. The 'id' parameter is not properly escaped before being used in a SQL query, and the query lacks proper preparation using $wpdb->prepare(). An authenticated user with Contributor-level access or higher can inject malicious SQL commands via the shortcode to extract sensitive data from the database.

MitigationUpdate the WPQuiz plugin to a version beyond 0.4.2 once a patched release is available. Until then, restrict shortcode usage permissions or disable the plugin for untrusted users.

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
WpquizWordPress extension
Affected:<= 0.4.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify WPQuiz plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WPQuiz' or 'Bauc Wpquiz' in the plugin list
    Affected if WPQuiz plugin appears in the installed plugins list
  2. Check installed WPQuiz version
    In Plugins list, locate WPQuiz and view the version number displayed beneath the plugin name, or check the plugin header in wp-content/plugins/wpquiz/wpquiz.php for 'Version: x.x.x'
    Affected if Version is 0.4.2 or lower
  3. Confirm shortcode is available
    Test if [wpquiz] shortcode is recognized by creating a test post/page with [wpquiz id="1"] and attempting to load it, or inspect plugin files for shortcode registration
    Affected if The [wpquiz] shortcode is registered and functional in the environment
  4. Check user role permissions for shortcode access
    Review WordPress user roles (Users > All Users) and check if Contributor-level or higher roles exist, or inspect if any role has permission to use shortcodes via plugin settings
    Affected if Authenticated users with Contributor role or higher can access the shortcode

You are affected if WPQuiz plugin version 0.4.2 or lower is installed and the wpquiz shortcode is accessible to authenticated users with Contributor-level permissions or higher.

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 0.4.2
Interim mitigation

Update the WPQuiz plugin to a version beyond 0.4.2 once a patched release is available. Until then, restrict shortcode usage permissions or disable the plugin for untrusted users.

Recommended fix Moderate confidence

Latest version newer than 0.4.2 (verify current stable release from wordpress.org)

  1. Check the current version of the WPQuiz plugin installed on your WordPress site
  2. Visit the WordPress plugin repository or contact the plugin developer to verify if a version newer than 0.4.2 is available
  3. If a newer version exists, update the plugin to the latest available version
  4. After updating, verify the fix by testing the wpquiz shortcode functionality
  5. Ensure you have a full backup of your site before performing any updates

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

Fix this in Wpquiz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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