CVE-2026-13174

Eventin <= 4.1.20 - Authenticated (Contributor+) Insecure Direct Object Reference to Speaker Account Deletion

2026-08-17 00:00
Muni Nitish Kumar Yaddala

Strategic Overview

Status
Patched in 4.1.21
Affected Plugin
Eventin – Event Calendar, Tickets, Registration, Booking & WooCommerce
Affected Version
<= 4.1.20
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-13174
View all Eventin – Event Calendar, Tickets, Registration, Booking & WooCommerce vulnerabilities

At a glance

CVE-2026-13174 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 4.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 preferring the `ids` body parameter over the URL path `id`, allowing the check to pass against the attacker's own account while the deletion executed against the victim's account in the path. This makes it possible for authenticated attackers, with contributor-level access and above, to delete arbitrary speaker or organizer user accounts by supplying their own user ID in the request body `ids` parameter while targeting a victim's account ID in the URL path.

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

https://www.cve.org/CVERecord?id=CVE-2026-13174https://www.wordfence.com/threat-intel/vulnerabilities/id/a2e2bd61-3187-4992-a3ae-1b5d88d1b90fhttps://nvd.nist.gov/vuln/detail/CVE-2026-13174

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C