CVE-2025-8977
BaseFortify
Publication date: 2025-08-28
Last updated on: 2025-08-29
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpress | simple_download_monitor | 3.9.34 |
| wordpress | simple_download_monitor | 3.9.33 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8977 is a time-based SQL Injection vulnerability in the Simple Download Monitor WordPress plugin (up to version 3.9.33). It occurs because the plugin insufficiently escapes and sanitizes the 'order' parameter, which is user-supplied. Authenticated users with Contributor-level access or higher, and permissions granted by an Administrator, can exploit this flaw by injecting additional SQL queries into existing database queries. This allows them to extract sensitive information from the database by manipulating the SQL query structure. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with Contributor-level access or higher to perform unauthorized SQL queries on the WordPress site's database. As a result, sensitive information stored in the database can be extracted without proper authorization. This can lead to data breaches, exposure of confidential data, and potential compromise of the website's integrity and user privacy. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual or suspicious POST requests to the Simple Download Monitor plugin's export logs feature, specifically those manipulating the 'order' or 'orderBy' parameters. Since the vulnerability involves time-based SQL injection via these parameters, detection can involve inspecting HTTP POST requests for unexpected or malicious SQL syntax in these fields. Additionally, reviewing logs for authenticated users with Contributor-level access or higher performing export log actions may help identify exploitation attempts. Commands to detect such activity could include using web server access logs or network monitoring tools to filter POST requests containing 'order' or 'orderBy' parameters. For example, using grep on Apache logs: `grep -i 'order=' /var/log/apache2/access.log` or using tools like Wireshark or tcpdump to capture HTTP POST data targeting the plugin's export logs endpoint. However, no specific detection commands are provided in the resources. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Simple Download Monitor WordPress plugin to version 3.9.34 or later, where the vulnerability has been fixed by properly sanitizing and escaping the 'order' and 'orderBy' parameters using WordPress functions like sanitize_text_field() and sanitize_sql_orderby(). Until the update can be applied, restrict Contributor-level and higher user permissions to trusted users only, and monitor export log activities closely. Additionally, ensure that WordPress nonces and capability checks are enforced to prevent unauthorized access to AJAX handlers related to log export and data deletion. [1]