CVE-2025-13417
SQL Injection in Plugin Organizer WordPress Plugin Allows Data Access
Publication date: 2025-12-29
Last updated on: 2025-12-29
Assigner: WPScan
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| plugin_organizer | plugin_organizer | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the Plugin Organizer WordPress plugin before version 10.2.4 is due to the plugin not sanitizing and escaping a parameter before using it in a SQL statement. This flaw allows users with subscriber-level access to perform SQL injection attacks, which means they can manipulate the database queries executed by the plugin.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with subscriber access to execute arbitrary SQL commands on the database. This could lead to unauthorized data access, data modification, or even deletion of data, potentially compromising the integrity and confidentiality of the website's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to reproduce the SQL injection using specially crafted requests. One method involves logging in as a subscriber and using curl commands to test for SQL injection by injecting a payload with a SLEEP function. For example, first log in and save authentication cookies with: curl -c cookies.txt -d "log=subscriber" -d "pwd=password" -d "wp-submit=Log+In" "http://your-site/wp-login.php". Then send an AJAX request with the injection payload: curl -b cookies.txt -d "action=PO_perform_plugin_search" -d "PO_plugin_path=a%' OR SLEEP(3) OR '1%'='1" "http://your-site/wp-admin/admin-ajax.php". If the server response is delayed (e.g., sleeps for 6 seconds), it confirms the SQL injection vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to update the Plugin Organizer WordPress plugin to version 10.2.4 or later, where the issue has been fixed. Avoid using vulnerable versions prior to 10.2.4 to prevent exploitation. [1]