dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2468

HIGH · 7.5 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Quentn WP plugin for WordPress is vulnerable to SQL Injection via the 'qntn_wp_access' cookie in all versions up to, and including, 1.2.12. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query in the `get_user_access()` method. 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.

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 Quentn WP WordPress plugin versions up to 1.2.12 contains an unauthenticated SQL Injection vulnerability in the get_user_access() method. The vulnerability stems from insufficient escaping of the user-controlled 'qntn_wp_access' cookie parameter combined with the lack of prepared statements in the SQL query, allowing attackers to inject arbitrary SQL commands.

MitigationUpdate the Quentn WP plugin to the latest version once a patch is released. As an interim measure, consider blocking or sanitizing the 'qntn_wp_access' cookie at the WAF level until the plugin can be updated.

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
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 Quentn WP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Quentn WP' in the list. Alternatively, check the wp-content/plugins directory for a folder named 'quentn-wp' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In the WordPress plugin list, click on the Quentn WP plugin to view its details, or open the main plugin PHP file (often named index.php or quentn-wp.php) and look for a version comment or constant near the top of the file.
    Affected if The version number is 1.2.12 or lower, or no version is displayed but the plugin appears to be the Quentn WP plugin
  3. Locate the vulnerable get_user_access method
    Search the plugin source files for the string 'function get_user_access' or 'get_user_access()' to locate the vulnerable method.
    Affected if The method exists in the plugin code and processes cookie data without prepared statements
  4. Verify the vulnerable cookie parameter usage
    Examine the get_user_access method code and confirm it reads the 'qntn_wp_access' cookie parameter and uses it in a SQL query without proper escaping or prepared statements.
    Affected if The code directly incorporates the cookie value into a SQL query without using $wpdb->prepare() or equivalent parameterized queries
  5. Confirm the attack surface is reachable without authentication
    Verify that this code path can be reached without requiring logged-in user status by checking if the function is hooked to a public-facing action or filter.
    Affected if The vulnerable code executes for unauthenticated (not-logged-in) visitors to the site

A user is affected if the Quentn WP plugin is installed with version 1.2.12 or lower AND the vulnerable get_user_access method uses the qntn_wp_access cookie in unsanitized SQL queries 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Quentn WP plugin to the latest version once a patch is released. As an interim measure, consider blocking or sanitizing the 'qntn_wp_access' cookie at the WAF level until the plugin can be updated.

Have this fixed 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 help mitigating

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-2026-2468 — 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-2026-2468 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