Strategic Overview
- Status
- Patched in 3.92.1
- Affected Plugin
- WordPress Automatic Plugin
- Affected Version
<= 3.92.0- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2024-27956
At a glance
CVE-2024-27956 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WordPress Automatic Plugin WordPress plugin, affecting versions <= 3.92.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.92.1; sites on affected versions should update now. Disclosed March 2024, reported by Rafie Muhammad.
Vulnerability Overview
The Automatic plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 3.92.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WordPress Automatic Plugin <= 3.92.0 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WordPress Automatic Plugin the fix is 3.92.1: builds <= 3.92.0 are affected, anything from 3.92.1 onward is not.
Remediation
Update to version 3.92.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WordPress Automatic Plugin 3.92.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WordPress Automatic Plugin
- 9.8CVE-2024-27954: Automatic <= 3.92.0 Arbitrary File Download and SSRF
CVE-2024-27954 - 9.1CVE-2021-4374: WordPress Automatic Plugin Arbitrary Options Update
CVE-2021-4374 - 8.8CVE-2025-5395: WordPress Automatic Plugin - AI… Arbitrary File Upload
CVE-2025-5395 - 8.8CVE-2024-27955: Automatic <= 3.92.0 CSRF to Privilege Escalation
CVE-2024-27955 - 7.2CVE-2026-56045: WordPress Automatic Plugin < 3.135.1 Stored XSS
CVE-2026-56045 - 6.4CVE-2024-4849: WordPress Automatic <= 3.94.0 Stored XSS
CVE-2024-4849 - 5.4CVE-2024-32693: WordPress Automatic Plugin <= 3.92.1 CSRF
CVE-2024-32693 - 4.7CVE-2025-6247: WordPress Automatic Plugin - AI… CSRF
CVE-2025-6247
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C