Strategic Overview
- Status
- Patched in 1.3.0
- Affected Plugin
- Autopost for X (formerly Autoshare for Twitter)
- Affected Version
<= 1.2.1- CVSS
- 9.8Critical
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2022-25912
At a glance
CVE-2022-25912 is a critical-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Autopost for X (formerly Autoshare for Twitter) WordPress plugin, affecting versions <= 1.2.1. 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 1.3.0; sites on affected versions should update now. Disclosed December 2022, reported by Sam Wheating.
Vulnerability Overview
The package simple-git is vulnerable to Remote Code Execution in versions before 3.15.0 when the ext transport protocol is enabled. This makes the vulnerability exploitable using the clone method. WordPress plugins and themes may be using this package, however, may not be vulnerable to exploitation.
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-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Autopost for X (formerly Autoshare for Twitter) <= 1.2.1 takes a caller who can reach the endpoint. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Autopost for X (formerly Autoshare for Twitter) the fix is 1.3.0: builds <= 1.2.1 are affected, anything from 1.3.0 onward is not.
Remediation
Update to version 1.3.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Autopost for X (formerly Autoshare for Twitter): WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Autopost for X (formerly Autoshare for Twitter) 1.3.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Autopost for X (formerly Autoshare for Twitter)
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C