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

CVE-2025-11920

HIGH · 8.8 CVSS v3.1 Published 2025-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
The WPCOM Member plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.7.14 via the action parameter in one of its shortcodes. 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 WPCOM Member WordPress plugin is vulnerable to Local File Inclusion (LFI) via the action parameter in one of its shortcodes. Authenticated attackers with Contributor-level access or higher can include and execute arbitrary .php files on the server, leading to Remote Code Execution (RCE).

MitigationUpdate the WPCOM Member plugin to a version newer than 1.7.14 once a patch is released. Until then, disable the vulnerable shortcode, restrict user permissions, and consider implementing WAF rules to block manipulation of the action parameter.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 WPCOM Member plugin installation and version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate WPCOM Member. Note the version number displayed, or inspect the plugin main PHP file header for the Version field.
    Affected if Plugin is installed and version is 1.7.14 or lower
  2. Identify active shortcodes using the vulnerable action parameter
    Search WordPress content (posts, pages, widgets) and theme template files for shortcode usage that includes an 'action' parameter. Use WP search or inspect database wp_posts table for shortcode references.
    Affected if A shortcode that accepts an action parameter is actively used in any published content
  3. Review user roles with Contributor access or higher
    Go to WordPress Admin > Users > All Users and examine which users have Contributor, Author, Editor, or Administrator roles. Identify any users who should not have these permissions.
    Affected if Any untrusted or compromised account has Contributor-level access or higher, enabling them to trigger the vulnerable shortcode
  4. Check for signs of exploitation in server logs
    Review web server access logs (Apache error.log, Nginx access.log) for requests containing patterns like 'action=' with directory traversal sequences (../) or references to .php files in unusual locations.
    Affected if Log entries show LFI attempts via the action parameter in the shortcode

A user is affected if the WPCOM Member plugin version is 1.7.14 or lower AND any user with Contributor-level or higher access can access content containing the vulnerable shortcode.

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 WPCOM Member plugin to a version newer than 1.7.14 once a patch is released. Until then, disable the vulnerable shortcode, restrict user permissions, and consider implementing WAF rules to block manipulation of the action parameter.

Recommended fix Moderate confidence

Version 1.7.15 or later (any version newer than 1.7.14)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WPCOM Member plugin
  4. Check the current version (should be 1.7.14 or below)
  5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/wpcom-member/
  6. After updating, verify the version number reflects the update

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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