CVE-2025-39570
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Lomu WPCOM Member wpcom-member allows PHP Local File Inclusion.This issue affects WPCOM Member: from n/a through <= 1.7.7.
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 confidencePHP Local File Inclusion vulnerability in the WPCOM Member WordPress plugin allows attackers to include arbitrary PHP files from the server by manipulating file inclusion parameters. Successful exploitation can lead to remote code execution if the attacker can upload files or access existing sensitive PHP files on the system.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WPCOM Member plugin is installedCheck for the presence of the wpcom-member directory in wp-content/plugins/ on your WordPress server, or view the installed plugins list in the WordPress admin dashboard under Plugins.Affected if The WPCOM Member plugin directory exists in the plugins folder.
-
Identify the installed version of WPCOM MemberLocate the main plugin PHP file (typically wpcom-member.php) and look for the 'Version' header in the plugin file comments, or check the plugin details in the WordPress admin Plugins page.Affected if The installed version matches or falls within any affected version range for this CVE.
-
Identify PHP files that handle file inclusion operationsSearch the wpcom-member plugin directory for PHP files containing include, require, include_once, or require_once statements with variable parameters (e.g., include($file), include($_GET['page']). Use grep or a code search tool.Affected if The plugin contains file inclusion code that uses unsanitized user input.
-
Verify if the file inclusion endpoints are accessibleReview your web server access logs for requests to the WPCOM Member plugin that contain directory traversal patterns such as ../ or absolute file paths in query parameters (e.g., ?file=../../wp-config.php).Affected if HTTP requests with traversal patterns targeting the plugin are present in access logs.
-
Check for signs of exploitation attemptsExamine web server access and error logs for successful inclusion of sensitive files like wp-config.php, .htaccess, or other PHP files outside the plugin directory.Affected if Log entries show successful inclusion of files outside the plugin directory.
You are affected if WPCOM Member plugin is installed, contains vulnerable file inclusion code using unsanitized input, and that functionality is accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of WPCOM Member if available; otherwise disable the plugin. Implement WAF rules to block directory traversal patterns in request parameters as a temporary mitigation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-39570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-39570 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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