CVE-2024-1316

Event Tickets and Registration <= 5.8.0 Events Tickets Plus <= 5.9.0 - Authenticated (Contributor+) Information Exposure

2024-02-08 00:00
Scott Kingsley Clark

Strategic Overview

Status
Patched in 5.8.1
Affected Plugin
Event Tickets and Registration
Affected Version
<= 5.8.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1316
View all Event Tickets and Registration vulnerabilities

At a glance

CVE-2024-1316 is a medium-severity Missing Authorization vulnerability in the Event Tickets and Registration WordPress plugin, affecting versions <= 5.8.0. 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 5.8.1; sites on affected versions should update now. Disclosed February 2024, reported by Scott Kingsley Clark.

Vulnerability Overview

The Event Tickets and Registration plugin for WordPress is vulnerable to Information Exposure in all versions up to 5.8.0 (free) & 5.9.1 (premium). This makes it possible for authenticated attackers, with contributor-level access and above, to view events they should not have access to such as password protected and trashed events.

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-862: Missing Authorization

Reaching this weakness in Event Tickets and Registration <= 5.8.0 takes an account at Contributor level or above. 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 Event Tickets and Registration the fix is 5.8.1: builds <= 5.8.0 are affected, anything from 5.8.1 onward is not.

Remediation

Update to version 5.8.1, 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.1 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-1316https://www.wordfence.com/threat-intel/vulnerabilities/id/5c9d08f5-7c94-40e7-979f-023456aeb54ehttps://nvd.nist.gov/vuln/detail/CVE-2024-1316

Related records

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