Eventin <= 4.1.22 - Missing Authorization to Unauthenticated Arbitrary Order Creation and Status Manipulation via 'status' Parameter
Strategic Overview
- Status
- Patched in 4.1.23
- Affected Version
<= 4.1.22- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-12956
At a glance
CVE-2026-12956 is a medium-severity Missing Authorization vulnerability in the Eventin WordPress plugin, affecting versions <= 4.1.22. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.1.23; sites on affected versions should update now. Disclosed September 2026, reported by Wordfence PRISM.
Vulnerability Overview
The WP Event Solution (Eventin) plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 4.1.22 via the create_item() handler for the /wp-json/eventin/v2/orders REST endpoint. The endpoint's create_item_permissions_check() function only verifies a wp_rest nonce (which is leaked to every visitor through the etn-public script's localized_data_obj on every frontend page) and accepts a user-supplied 'status' value in prepare_item_for_database() with no whitelist validation. This makes it possible for unauthenticated attackers to create etn-order posts with status='completed' that are counted as sold by etn_get_sold_tickets_by_event(); because the auto-cleanup wp_schedule_single_event() in create_item() only fires for status='pending' orders, the forged completed orders persist indefinitely and exhaust ticket inventory.
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.
CWE-862: Missing Authorization
Eventin <= 4.1.22 carries this weakness at status, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Eventin the fix is 4.1.23: builds <= 4.1.22 are affected, anything from 4.1.23 onward is not.
Remediation
Update to version 4.1.23, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Eventin 4.1.23 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Eventin – Event Calendar, Tickets, Registration, Booking & WooCommerce
- 8.8CVE-2025-4796: Eventin <= 4.0.34 Privilege Escalation
CVE-2025-4796 - 8.8CVE-2025-39584: Eventin <= 4.0.25 Local File Inclusion
CVE-2025-39584 - 8.8CVE-2025-1770: Event Manager LFI
CVE-2025-1770 - 8.8CVE-2025-26964: Eventin <= 4.0.20 Local File Inclusion
CVE-2025-26964 - 8.8CVE-2024-56213: Eventin <= 4.0.7 Local File Inclusion
CVE-2024-56213 - 8.8CVE-2024-7149: Event Manager LFI
CVE-2024-7149 - 7.5CVE-2026-15667: Eventin <= 4.1.22 Local File Inclusion
CVE-2026-15667 - 7.5CVE-2026-15406: Eventin <= 4.1.22 Local File Inclusion
CVE-2026-15406
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C