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

CVE-2025-58608

HIGH · 7.5 CVSS v3.1 Published 2025-09-03
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 BuddyDev MediaPress mediapress allows PHP Local File Inclusion.This issue affects MediaPress: from n/a through <= 1.5.9.1.

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 Local File Inclusion (LFI) vulnerability in the MediaPress WordPress plugin. The plugin improperly controls filenames used in PHP include/require statements, allowing attackers to include arbitrary local PHP files. This can lead to arbitrary code execution if an attacker can upload malicious files or access existing sensitive PHP files on the server.

MitigationUpgrade MediaPress to the latest patched version as soon as available. In the interim, disable PHP's allow_url_include setting and consider implementing WAF rules to block directory traversal patterns in HTTP requests.

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 MediaPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for MediaPress. Alternatively, check the /wp-content/plugins/mediapress/ directory exists and contains plugin files.
    Affected if MediaPress plugin is not installed or not active - the vulnerability does not apply
  2. Determine MediaPress version
    Check the plugin version in the plugin header (plugins.php page in WP admin) or read the main plugin file (e.g., /wp-content/plugins/mediapress/mediapress.php) and look for the Version: comment. Compare to the affected version range if known.
    Affected if The installed version falls within the affected version range and no patch has been applied
  3. Identify vulnerable endpoint exposure
    Review HTTP access logs for requests containing '../' directory traversal patterns targeting the MediaPress plugin paths (typically /?mpp_* or /?mediapress_* parameters). Check if the plugin's file inclusion functions are accessible without authentication.
    Affected if The file inclusion endpoint is exposed and accessible (often without auth), allowing path traversal in URL parameters
  4. Check PHP configuration
    Review php.ini or run php -i | grep allow_url_include to verify if PHP's allow_url_include setting is enabled (value of 1). Also check for allow_url_fopen.
    Affected if allow_url_include is enabled - combined with the LFI flaw, this increases the attack surface for remote code execution
  5. Audit for suspicious uploaded files
    Inspect /wp-content/uploads/mediapress/ directories and any temp/upload directories for unfamiliar .php files with random names, encoded content, or webshell patterns. Compare file hashes against known good baselines if available.
    Affected if Unexpected PHP files exist in upload directories, indicating potential exploitation

A user is affected if MediaPress is installed, the version is within the affected range, and the vulnerable file inclusion endpoint is accessible without proper access controls.

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

Upgrade MediaPress to the latest patched version as soon as available. In the interim, disable PHP's allow_url_include setting and consider implementing WAF rules to block directory traversal patterns in HTTP requests.

Recommended fix Moderate confidence

MediaPress version greater than 1.5.9.1 (check BuddyDev for latest stable release)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate MediaPress (mediapress) plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update completes successfully
  6. 6. Test MediaPress functionality (upload media, view galleries) to ensure the plugin works correctly after update
  7. 7. If no update is available from WordPress.org, check BuddyDev's official website (buddydev.com) for the latest patched release
Caveat Review BuddyDev release notes for any backward-incompatible changes in the new version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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