CVE-2024-12578

Tickera – WordPress Event Ticketing <= 3.5.4.8 - Unauthenticated Customer Data Exposure

2024-12-13 00:00
Paule

Strategic Overview

Status
Patched in 3.5.4.9
Affected Version
<= 3.5.4.8
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-12578
View all Tickera – Sell Tickets & Manage Events vulnerabilities

At a glance

CVE-2024-12578 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Tickera WordPress plugin, affecting versions <= 3.5.4.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.5.4.9; sites on affected versions should update now. Disclosed December 2024, reported by Paule.

Vulnerability Overview

The Tickera – WordPress Event Ticketing plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 3.5.4.8 via the 'tickera_tickets_info' endpoint. This makes it possible for unauthenticated attackers to extract sensitive data from bookings like full names, email addresses, check-in/out timestamps and more.

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 privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Tickera <= 3.5.4.8 carries this weakness at tickera_tickets_info, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Tickera the fix is 3.5.4.9: builds <= 3.5.4.8 are affected, anything from 3.5.4.9 onward is not.

Remediation

Update to version 3.5.4.9, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Tickera 3.5.4.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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