dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-11704

HIGH · 7.5 CVSS v3.1 Published 2025-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 Elegance Menu plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.9 via the 'elegance-menu' attribute of the `elegance-menu` shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

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 Elegance Menu WordPress plugin versions up to 1.9 contain a Local File Inclusion (LFI) vulnerability in the elegance-menu shortcode. Authenticated attackers with Contributor-level access or higher can manipulate the elegance-menu attribute to include and execute arbitrary .php files on the server, achieving remote code execution.

MitigationDisable or restrict access to the elegance-menu shortcode until a patched version is released; implement strict input validation to prevent path traversal in shortcode attributes.

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

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

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 Elegance Menu plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for the Elegance Menu plugin
    Affected if The Elegance Menu plugin appears in the list of installed plugins
  2. Check installed version against affected range
    In the installed plugins list, locate the Elegance Menu plugin and note the version number displayed
    Affected if The installed version is 1.9 or lower (any version up to and including 1.9)
  3. Confirm the elegance-menu shortcode is active
    Inspect the plugin files for shortcode registration (search for 'add_shortcode' with 'elegance-menu'), or attempt to use [elegance-menu] in a test post
    Affected if The shortcode is registered and functional in the WordPress installation
  4. Identify users with Contributor-level access or higher
    In WordPress admin, go to Users > All Users and review user roles
    Affected if At least one user account has Contributor, Author, Editor, or Administrator role

The environment is affected if Elegance Menu plugin version 1.9 or lower is installed, the shortcode is active, and any Contributor-level or higher user account exists in WordPress.

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

Disable or restrict access to the elegance-menu shortcode until a patched version is released; implement strict input validation to prevent path traversal in shortcode attributes.

Recommended fix High confidence

Version 2.0 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Elegance Menu plugin
  4. Check if an update is available - if so, update to the latest version
  5. If no update is shown in WordPress, manually download the latest version from wordpress.org/plugins/elegance-menu/ and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 2.0 or later
  7. Confirm the vulnerability is patched by testing that the elegance-menu shortcode no longer accepts arbitrary file paths in the elegance-menu attribute
Caveat Minimal risk - plugin updates typically maintain backward compatibility with existing shortcodes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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