CVE-2025-47627
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 LCweb PrivateContent - Mail Actions allows PHP Local File Inclusion. This issue affects PrivateContent - Mail Actions: from n/a through 2.3.2.
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 confidenceA Local File Inclusion (LFI) vulnerability exists in the PrivateContent - Mail Actions WordPress plugin. The plugin improperly handles user-supplied input in PHP include/require statements, allowing attackers to traverse the filesystem and include arbitrary local PHP files. This can lead to sensitive file disclosure and potentially remote code execution depending on server configuration.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Identify if PrivateContent - Mail Actions plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'PrivateContent - Mail Actions' in the list, or check the /wp-content/plugins/ directory for a folder named 'private-content-mail-actions' or similar variantAffected if The plugin appears in the installed plugins list
-
Determine the installed plugin versionIn the WordPress plugins list, click on the plugin to view its details and locate the version number displayed there, or inspect the main plugin PHP file header for a 'Version:' tagAffected if The version number cannot be confirmed as patched or is within an unpatched version range (older versions are vulnerable)
-
Locate the file inclusion code pathsExamine the plugin PHP files, particularly any files handling include/require statements that accept user input via GET/POST parameters. Look for patterns like 'include($_GET[...])' or 'require($_POST[...])' within the plugin directoryAffected if User-controllable input is used directly in include/require statements without proper sanitization
-
Identify accessible entry points for the vulnerabilityReview the plugin's publicly accessible PHP files and URL parameters to identify which ones accept file path arguments. Check for parameters that might accept file paths or traversal sequences like '../'Affected if The plugin exposes any parameter that accepts file paths without validation and includes them server-side
The environment is affected if the PrivateContent - Mail Actions plugin is installed and its file inclusion functionality uses unsanitized user input to determine which files to include, allowing directory traversal attacks.
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 PrivateContent - Mail Actions that properly validates and sanitizes file paths used in include/require statements, or implement web application firewall rules to block directory traversal patterns in the meantime.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47627 — 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-47627 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