Eventin <= 4.1.20 - Insecure Direct Object Reference to Authenticated (Contributor+) Schedule Deletion and Modification
Strategic Overview
- Status
- Patched in 4.1.21
- Affected Version
<= 4.1.20- CVSS
- 6.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-13175
At a glance
CVE-2026-13175 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Eventin WordPress plugin, affecting versions <= 4.1.20. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.1.21; sites on affected versions should update now. Disclosed August 2026, reported by Muni Nitish Kumar Yaddala.
Vulnerability Overview
The Eventin plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 4.1.20. This is due to the permission check reading the subject ID from the request body parameter `ids` while the handler read it from the URL parameter `id`, allowing an attacker to authorize against their own schedule and execute against a victim's. This makes it possible for authenticated attackers, with contributor-level access and above, to delete or modify schedules belonging to other users by supplying a victim's schedule ID in the URL path while carrying their own schedule ID in the request body to pass the ownership check.
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.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Eventin <= 4.1.20 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Eventin the fix is 4.1.21: builds <= 4.1.20 are affected, anything from 4.1.21 onward is not.
Remediation
Update to version 4.1.21, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Eventin 4.1.21 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
- 9.8CVE-2025-47539: Eventin <= 4.0.26 Unauthenticated Privilege Escalation
CVE-2025-47539 - 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-2025-68047: Eventin <= 4.1.3 PHP Object Injection
CVE-2025-68047 - 7.5CVE-2025-49869: Eventin <= 4.0.31 PHP Object Injection
CVE-2025-49869
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C