dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-23910

HIGH · 8.5 CVSS v3.1 Published 2025-01-22
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 keighl Menus Plus+ menus-plus allows SQL Injection.This issue affects Menus Plus+: from n/a through <= 1.9.6.

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 · moderate confidence

SQL injection vulnerability in the Menus Plus+ WordPress plugin allows unauthenticated attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized data access, modification, or deletion from the database.

MitigationUpgrade Menus Plus+ to the latest patched version; if no patch available, implement parameterized queries or prepared statements at all database interaction points within the plugin code.

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. Identify Menus Plus+ installation status and version
    Check the WordPress plugins directory or wp-admin for Menus Plus+ plugin. In the filesystem, examine /wp-content/plugins/ directory for the menus-plus or similar folder, and read the main plugin file header for the Version field. Alternatively, query the wp_options table for 'active_plugins' and check plugin files for version metadata.
    Affected if Menus Plus+ is installed and the version falls within any known affected range (unpatched versions).
  2. Verify plugin is active
    Check WordPress wp_options table for the 'active_plugins' option, or log into wp-admin > Plugins to confirm Menus Plus+ is activated. The vulnerability is exploitable only against active plugin installations.
    Affected if Menus Plus+ plugin is installed and active on the WordPress site.
  3. Inspect vulnerable SQL interaction points
    Examine the main plugin PHP files (typically in wp-content/plugins/menus-plus/ or similar naming) for direct SQL queries using $wpdb->prepare, mysql_* functions, or unsanitized variable interpolation into SQL strings. Focus on files handling menu-related user input or request parameters.
    Affected if Plugin code contains SQL queries that incorporate user-supplied input without proper sanitization or prepared statements.
  4. Check for unauthenticated access exposure
    Review plugin PHP files for hooks or endpoints accessible to unauthenticated users (no check for 'is_user_logged_in()', 'current_user_can()', or capability checks). Look for AJAX actions registered with 'wp_ajax_nopriv_' or direct file access without authentication guards.
    Affected if The vulnerable SQL code path is reachable without authentication (no login required).
  5. Review HTTP request handling for the attack vector
    Examine how the plugin handles GET or POST parameters (such as menu_id, item_id, or custom parameters) and passes them to database queries. Check if these parameters are filtered through $wpdb->prepare() or add_slashes/escape functions before SQL execution.
    Affected if User input from HTTP requests flows directly into SQL queries without sanitization.

A user is affected if Menus Plus+ is installed, active, contains unsanitized SQL queries handling unauthenticated user input, and the installed version is known to be vulnerable to CVE-2025-23910.

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

Upgrade Menus Plus+ to the latest patched version; if no patch available, implement parameterized queries or prepared statements at all database interaction points within the plugin code.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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