CVE-2025-9776
BaseFortify
Publication date: 2025-09-11
Last updated on: 2025-09-11
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | catfolders | * |
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?
The vulnerability in the CatFolders WordPress plugin (up to version 2.5.2) is a time-based SQL Injection via the CSV Import feature. It occurs because the plugin does not properly escape user-supplied parameters and does not sufficiently prepare the existing SQL query. This allows authenticated users with Author-level access or higher to append additional SQL queries to existing ones, potentially extracting sensitive information from the database.
How can this vulnerability impact me? :
This vulnerability can allow an authenticated attacker with Author-level or higher permissions to perform unauthorized SQL queries on the WordPress database. As a result, the attacker could extract sensitive information from the database, potentially compromising data confidentiality. However, it does not allow modification or deletion of data (no integrity or availability impact).
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for REST API calls to the CatFolders plugin's CSV import endpoint, specifically POST requests to the `/import-csv` REST API route, which is vulnerable to time-based SQL Injection when an authenticated user with Author-level access or higher uploads a crafted CSV file. Detection can involve checking web server logs or WordPress REST API logs for suspicious POST requests to endpoints under the `CATF_ROUTE_NAMESPACE` namespace, especially `/import-csv`. Additionally, monitoring for unusual database query delays or anomalies during CSV import operations may indicate exploitation attempts. Since the vulnerability requires authenticated access with upload_files capability, reviewing user activity logs for such users performing CSV imports is recommended. Specific commands depend on your environment, but examples include: 1) Using grep on web server logs to find suspicious REST API calls: `grep '/wp-json/catfolders/import-csv' /var/log/apache2/access.log` 2) Using WP-CLI or database query logs to monitor for slow queries or unusual SQL statements during CSV import. 3) Enabling WordPress debug logging to capture REST API request details. Note: The exact REST API namespace prefix (`CATF_ROUTE_NAMESPACE`) is not specified in the provided text, so replace it with the actual namespace used in your installation. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Restrict access to the CSV import REST API endpoint (`/import-csv`) to only trusted users with necessary permissions, ensuring only authorized users with upload_files capability can access it. 2) Temporarily disable or restrict the CatFolders plugin's CSV import functionality until a patch or update is applied. 3) Update the CatFolders plugin to a version later than 2.5.2 once available, as versions up to and including 2.5.2 are vulnerable. 4) Monitor user accounts with Author-level access or higher for suspicious activity related to media library imports. 5) Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the CSV import endpoint. 6) Review and harden user permissions to minimize the number of users with upload_files capability. These steps help prevent exploitation by limiting the ability to perform malicious CSV imports that exploit the time-based SQL injection vulnerability. [1]