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

CVE-2025-47439

HIGH · 7.5 CVSS v3.1 Published 2025-05-07
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Chill Download Monitor download-monitor allows PHP Local File Inclusion.This issue affects Download Monitor: from n/a through <= 5.0.22.

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

This is a PHP Local File Inclusion (LFI) vulnerability in the Download Monitor WordPress plugin. The plugin fails to properly validate filenames used in include/require statements, allowing attackers to manipulate file path parameters and potentially execute arbitrary PHP code by including malicious local files.

MitigationUpdate the Download Monitor plugin to the latest patched version once released. Until then, implement web application firewall rules to block suspicious file inclusion requests and review server logs for signs of exploitation.

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 Download Monitor plugin is installed
    Check wp-content/plugins/ directory for download-monitor folder, or query WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' and option_value LIKE '%download-monitor%';
    Affected if Plugin folder exists in plugins directory or is listed in active plugins
  2. Determine installed plugin version
    Read version from download-monitor/readme.txt or download-monitor/plugin.php header, or query: SELECT * FROM wp_options WHERE option_name LIKE '%download_monitor%version%';
    Affected if Version number cannot be determined or falls within unpatched release range
  3. Identify plugin endpoints accepting file parameters
    Review plugin source files in wp-content/plugins/download-monitor/ for include/require statements using $_GET, $_POST, or $_REQUEST variables without proper sanitization
    Affected if Code contains include/require with unsanitized user input parameters
  4. Check for known vulnerable parameters
    Search plugin PHP files for patterns like 'include($_REQUEST', 'require($_GET', 'include($file', 'require_once($_POST' without basename(), realpath(), or whitelist validation
    Affected if File inclusion functions use raw user input without validation
  5. Review web server access logs for exploitation attempts
    Grep access logs (usually in /var/log/apache2/ or /var/log/nginx/) for patterns like: ?file=../../, ?file=/etc/passwd, ?include=, ?path=../../../
    Affected if Logs contain requests with directory traversal sequences targeting the plugin endpoints

Environment is affected if Download Monitor plugin is active and the version has known LFI vulnerability in file inclusion functionality without proper filename validation.

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

Update the Download Monitor plugin to the latest patched version once released. Until then, implement web application firewall rules to block suspicious file inclusion requests and review server logs for signs of exploitation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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