Summary
CVE-2026-12987 is a high-severity chained vulnerability in the Events Manager WordPress plugin (all versions before 7.3.7) that combines PHP Object Injection with unauthenticated SQL Injection. On sites operating in No-User-Account Booking Mode, an attacker with no credentials can submit a maliciously crafted booking registration field which, upon deserialization by the plugin, triggers a gadget chain leading to an unparameterized database query — exposing sensitive data including user password hashes and WordPress secret keys. The vulnerability carries a CVSS v3.1 score of 7.5 (High).
Technical details
- Root cause: Booking-registration fields submitted by users are stored as booking metadata and later deserialized without restricting the allowed PHP classes, enabling PHP Object Injection (CWE-89).
- Trigger condition: The site must be running in No-User-Account Booking Mode — a configuration that permits event bookings without requiring visitor account creation.
- Attack chain: The injected PHP object triggers a gadget chain that reaches a database query constructed without parameterization, resulting in SQL Injection and arbitrary database read.
- Attack vector: Fully unauthenticated and network-accessible — no privileges or user interaction are required (CVSS AV:N/AC:L/PR:N/UI:N).
- Impact: An unauthenticated attacker can extract arbitrary data from the WordPress database, including user password hashes and WordPress secret keys. Successful exfiltration of these values could enable full site compromise through offline credential cracking or secret key abuse.
Affected software
- Events Manager WordPress plugin — all versions before 7.3.7
Severity
CVSS v3.1 base score: 7.5 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Mitigation and recommended actions
- Immediate: Update the Events Manager WordPress plugin to version 7.3.7 or later, which contains the vendor-issued security fix.
- Sites using No-User-Account Booking Mode face direct exposure and should treat this patch as urgent.
- If immediate patching is not feasible, consider temporarily disabling No-User-Account Booking Mode or restricting access to booking registration endpoints via a web application firewall or network-layer controls as an interim measure.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

