CVE-2024-2261

Event Tickets and Registration <= 5.8.2 - Improper Authorization to Information Disclosure

2024-03-26 00:00
Tim Coen

Strategic Overview

Status
Patched in 5.8.3
Affected Plugin
Event Tickets and Registration
Affected Version
<= 5.8.2
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-2261
View all Event Tickets and Registration vulnerabilities

At a glance

CVE-2024-2261 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Event Tickets and Registration WordPress plugin, affecting versions <= 5.8.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 5.8.3; sites on affected versions should update now. Disclosed March 2024, reported by Tim Coen.

Vulnerability Overview

The Event Tickets and Registration plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.8.2 via the RSVP functionality. This makes it possible for authenticated attackers, with contributor access and above, to extract sensitive data including emails and street addresses.

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 Event Tickets and Registration <= 5.8.2 takes a caller who can reach the endpoint. 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 Event Tickets and Registration the fix is 5.8.3: builds <= 5.8.2 are affected, anything from 5.8.3 onward is not.

Remediation

Update to version 5.8.3, 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: Event Tickets and Registration 5.8.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-2261https://www.wordfence.com/threat-intel/vulnerabilities/id/2e42dd1c-adf7-471a-a14a-9038c56413a2https://nvd.nist.gov/vuln/detail/CVE-2024-2261

Related records

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