Nexter Extension <= 2.0.3 - Authenticated(Editor+) Remote Code Execution via metabox
Strategic Overview
- Status
- Patched in 2.0.4
- Affected Version
<= 2.0.3- CVSS
- 7.2High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2023-45751
At a glance
CVE-2023-45751 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Nexter Extension WordPress plugin, affecting versions <= 2.0.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 2.0.4; sites on affected versions should update now. Disclosed October 2023, reported by Rafie Muhammad.
Vulnerability Overview
The Nexter Extension plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 2.0.3 via the nxt-code-php-snippet metabox. This allows authenticated attackers with editor-level privileges and above to execute code on the server.
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 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 Nexter Extension <= 2.0.3 takes an account at Editor level or above. 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 Nexter Extension the fix is 2.0.4: builds <= 2.0.3 are affected, anything from 2.0.4 onward is not.
Remediation
Update to version 2.0.4, or a newer patched version
How does WordSec protect against this?
An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: 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: Nexter Extension 2.0.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Nexter Extension – Security, Performance, Code Snippets & Site Toolkit
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C