dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4304

HIGH · 7.5 CVSS v3.1 Published 2026-05-05
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 WeePie Cookie Allow plugin for WordPress is vulnerable to SQL Injection via the 'consent' parameter in all versions up to, and including, 3.4.11 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.

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 WeePie Cookie Allow WordPress plugin (versions up to 3.4.11) contains a SQL injection vulnerability in the 'consent' parameter. The plugin fails to properly escape user input and does not use prepared statements, allowing unauthenticated attackers to inject arbitrary SQL queries and extract sensitive data from the database.

MitigationUpdate the WeePie Cookie Allow plugin to version 3.4.12 or later. If no update is available, manually escape the 'consent' parameter and convert the SQL query to use prepared statements.

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. Locate the WeePie Cookie Allow plugin
    Check your WordPress installation at wp-content/plugins/ for a folder named 'wepie-cookie-allow' or similar. You can also list installed plugins via WP-CLI: wp plugin list --name='*cookie*'
    Affected if The plugin folder exists in your plugins directory
  2. Identify the installed version
    Open the main plugin file (usually wepie-cookie-allow.php) and look for the version comment in the file header, or check the readme.txt file for the 'Stable tag' entry
    Affected if The version listed is 3.4.11 or earlier
  3. Verify if the plugin is active
    Check your WordPress admin under Plugins > Installed Plugins, or query the wp_options table for the option_name 'active_plugins', or use WP-CLI: wp plugin status wepie-cookie-allow
    Affected if The plugin shows as 'Active' in WordPress
  4. Confirm the vulnerable parameter exists
    Examine the plugin source code for the file handling the consent parameter (commonly in the main plugin file or a dedicated consent handler). Look for code that processes the 'consent' GET or POST parameter directly into an SQL query without prepare()
    Affected if The code directly uses the 'consent' parameter in a SQL query without using $wpdb->prepare() or equivalent escaping

Your environment is affected if the WeePie Cookie Allow plugin is installed, active, and the version is 3.4.11 or earlier, with the 'consent' parameter being processed unsafely in SQL queries.

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 WeePie Cookie Allow plugin to version 3.4.12 or later. If no update is available, manually escape the 'consent' parameter and convert the SQL query to use prepared statements.

Recommended fix Moderate confidence

WeePie Cookie Allow version 3.4.12 or later

  1. 1. Update the WeePie Cookie Allow WordPress plugin to the latest available version (version 3.4.12 or higher)
  2. 2. Verify the update was applied successfully through WordPress plugin management
  3. 3. Test the 'consent' functionality to ensure the plugin continues to work correctly after the update
  4. 4. Consider reviewing access logs for any signs of exploitation attempts targeting this vulnerability

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

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

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