dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-27281

HIGH · 8.5 CVSS v3.1 Published 2025-03-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in cookforweb All In Menu all-in-menu allows Blind SQL Injection.This issue affects All In Menu: from n/a through <= 1.1.5.

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

A blind SQL injection vulnerability exists in the cookforweb All In Menu plugin (versions through 1.1.5). The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters, potentially enabling data exfiltration from the database.

MitigationUpdate the All In Menu plugin to the latest patched version. If no update is available, manually audit and remediate the vulnerable code by implementing parameterized queries or prepared statements for all database interactions, and apply proper input validation.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

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. Check if All In Menu plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'all-in-menu' or similar cookforweb menu plugin.
    Affected if The cookforweb All In Menu plugin appears in the installed plugins list.
  2. Locate the installed plugin version
    In the WordPress admin, find the plugin version listed on the Plugins page. Alternatively, open the main plugin PHP file (usually in wp-content/plugins/all-in-menu/ or similar) and check the plugin header comment for 'Version:' or check the readme.txt file.
    Affected if A version number is found for the All In Menu plugin.
  3. Compare installed version against affected range
    Compare the identified version number to the affected range: versions 1.1.5 and below are vulnerable. If your version is 1.1.5 or lower, you are in the affected range.
    Affected if The installed version is 1.1.5 or lower.
  4. Identify accessible user input points
    Review the plugin's frontend forms, URL parameters, or AJAX endpoints that accept user input. The vulnerability exists in unsanitized inputs processed by the plugin.
    Affected if The plugin processes user input through GET/POST parameters without visible sanitization.

You are affected if the cookforweb All In Menu plugin is installed and the installed version is 1.1.5 or lower.

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 All In Menu plugin to the latest patched version. If no update is available, manually audit and remediate the vulnerable code by implementing parameterized queries or prepared statements for all database interactions, and apply proper input validation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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