CVE-2024-1053

Event Tickets and Registration <= 5.8.1 - Missing Authorization

2024-02-21 00:00
Muhammad Daffa

Strategic Overview

Status
Patched in 5.8.2
Affected Plugin
Event Tickets and Registration
Affected Version
<= 5.8.1
CVSS
4.3Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2024-1053
View all Event Tickets and Registration vulnerabilities

At a glance

CVE-2024-1053 is a medium-severity Improper Access Control vulnerability in the Event Tickets and Registration WordPress plugin, affecting versions <= 5.8.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 5.8.2; sites on affected versions should update now. Disclosed February 2024, reported by Muhammad Daffa.

Vulnerability Overview

The Event Tickets and Registration plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'email' action in all versions up to, and including, 5.8.1. This makes it possible for authenticated attackers, with contributor-level access and above, to email the attendees list to themselves.

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-284: Improper Access Control

Event Tickets and Registration <= 5.8.1 carries this weakness at email, and reaching it takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Event Tickets and Registration the fix is 5.8.2: builds <= 5.8.1 are affected, anything from 5.8.2 onward is not.

Remediation

Update to version 5.8.2, 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.2 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-1053https://www.wordfence.com/threat-intel/vulnerabilities/id/a7839847-2637-4a0d-bfc1-5f80b8433e24https://nvd.nist.gov/vuln/detail/CVE-2024-1053

Related records

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