CVE-2025-58608
BaseFortify
Publication date: 2025-09-03
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| buddydev | mediapress | 1.6.0 |
| buddydev | mediapress | 1.5.9.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-98 | The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Local File Inclusion (LFI) issue in the WordPress MediaPress Plugin versions up to 1.5.9.1. It allows an attacker with contributor-level privileges to include and display local files from the target website. These files may contain sensitive information such as database credentials, potentially enabling a full database takeover depending on the website's configuration. [1]
How can this vulnerability impact me? :
The vulnerability can lead to exposure of sensitive files on the server, including database credentials. This exposure can result in a complete database takeover, compromising the confidentiality, integrity, and availability of the website and its data. Although considered low priority and unlikely to be widely exploited, it poses a risk of opportunistic automated attacks. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this Local File Inclusion (LFI) vulnerability can involve monitoring for attempts to exploit the include/require statements in the MediaPress plugin. Since the vulnerability allows an attacker with contributor-level privileges to include local files, you can look for suspicious HTTP requests containing file path parameters or attempts to access sensitive files. Specific commands are not provided in the resources, but general approaches include using web server logs to grep for suspicious patterns, e.g., commands like `grep -i 'include' /var/log/apache2/access.log` or monitoring for unusual file access patterns. Additionally, scanning the installed MediaPress plugin version to confirm if it is ≤ 1.5.9.1 can help identify vulnerable installations. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the MediaPress plugin to version 1.6.0 or later, where the vulnerability is fixed. If updating is not immediately possible, applying Patchstack's virtual patching (vPatching) can provide an automatic protective measure against exploitation. Limiting contributor-level privileges and monitoring for suspicious activity can also help reduce risk until the patch is applied. [1]