Event Tickets with Ticket Scanner <= 2.3.11 - Authenticated (Author+) Remote Code Execution
Strategic Overview
- Status
- Patched in 2.3.12
- Affected Plugin
- Event Tickets with Ticket Scanner
- Affected Version
<= 2.3.11- CVSS
- 8.8High
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2024-52427
At a glance
CVE-2024-52427 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Event Tickets with Ticket Scanner WordPress plugin, affecting versions <= 2.3.11. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.3.12; sites on affected versions should update now. Disclosed November 2024, reported by Hakiduck.
Vulnerability Overview
The Event Tickets with Ticket Scanner plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.3.11. This makes it possible for authenticated attackers, with author-level access 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 Event Tickets with Ticket Scanner <= 2.3.11 takes an account at Author 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 Event Tickets with Ticket Scanner the fix is 2.3.12: builds <= 2.3.11 are affected, anything from 2.3.12 onward is not.
Remediation
Update to version 2.3.12, or a newer patched version
How does WordSec protect against this?
An attacker needs Author 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: Event Tickets with Ticket Scanner 2.3.12 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Event Tickets with Ticket Scanner
- 6.4Event Tickets with Ticket Scanner <= 1.5.4 Stored Cross-Site Scripting
- 6.1CVE-2024-35652: Event Tickets with Ticket Scanner Reflected XSS
CVE-2024-35652 - 5.4CVE-2024-9866: Event Tickets… Authenticated (Subscriber+) Stored XSS
CVE-2024-9866 - 4.4CVE-2024-6711: Event Tickets with Ticket Scanner <= 2.3.7 Stored XSS
CVE-2024-6711 - 4.3CVE-2025-1762: Event Tickets with Ticket Scanner CSRF
CVE-2025-1762
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C