CVE-2024-5860

Tickera <= 3.5.2.8 - Missing Authorization to Authenticated (Susbcriber+) Ticket Deletion

2024-06-17 00:00
Lucio Sá

Strategic Overview

Status
Patched in 3.5.2.9
Affected Plugin
Tickera – Sell Tickets & Manage Events
Affected Version
<= 3.5.2.8
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-5860
View all Tickera – Sell Tickets & Manage Events vulnerabilities

At a glance

CVE-2024-5860 is a medium-severity Missing Authorization vulnerability in the Tickera WordPress plugin, affecting versions <= 3.5.2.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Susbcriber level or above. The issue is fixed in version 3.5.2.9; sites on affected versions should update now. Disclosed June 2024, reported by Lucio Sá.

Vulnerability Overview

The Tickera – WordPress Event Ticketing plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the tc_dl_delete_tickets AJAX action in all versions up to, and including, 3.5.2.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete all tickets associated with 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 Tickera <= 3.5.2.8 takes an account at Susbcriber 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 Tickera the fix is 3.5.2.9: builds <= 3.5.2.8 are affected, anything from 3.5.2.9 onward is not.

Remediation

Update to version 3.5.2.9, 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: Tickera 3.5.2.9 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-5860https://www.wordfence.com/threat-intel/vulnerabilities/id/d86aa41c-24df-49ec-b273-7bb57adddddehttps://nvd.nist.gov/vuln/detail/CVE-2024-5860

Related records

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