CVE-2025-11517

Event Tickets and Registration <= 5.26.5 - Unauthenticated Ticket Payment Bypass

2025-10-17 18:07
AlexHenry

Strategic Overview

Status
Patched in 5.26.6
Affected Version
<= 5.26.5
CVSS
7.5High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-11517
View all Event Tickets and Registration vulnerabilities

At a glance

CVE-2025-11517 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the Event Tickets and Registration WordPress plugin, affecting versions <= 5.26.5. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 5.26.6; sites on affected versions should update now. Disclosed October 2025, reported by AlexHenry.

Vulnerability Overview

The Event Tickets and Registration plugin for WordPress is vulnerable to payment bypass in all versions up to, and including, 5.26.5. This is due to the /wp-json/tribe/tickets/v1/commerce/free/order endpoint not verifying that a ticket type should be free allowing the user to bypass the payment. This makes it possible for unauthenticated attackers to obtain access to paid tickets, without paying for them, causing a loss of revenue for the target.

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. A successful exploit has high impact on integrity.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Event Tickets and Registration <= 5.26.5 takes no account at all. 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.26.6: builds <= 5.26.5 are affected, anything from 5.26.6 onward is not.

Remediation

Update to version 5.26.6, 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: Event Tickets and Registration 5.26.6 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