# CVE-2025-11517: Event Tickets and Registration <= 5.26.5 - Unauthenticated Ticket Payment Bypass

> Unauthenticated attackers can bypass payment checks to obtain paid tickets for free, causing revenue loss for site owners.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-jfwp-6m6h-2wgw

## What is CVE-2025-11517?

CVE-2025-11517 is a high-severity vulnerability in stellarwp Event Tickets and Registration, published on 18 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-11517?


## How do I fix CVE-2025-11517?

No fix has been published for CVE-2025-11517 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11517 being exploited?

There is no known exploitation of CVE-2025-11517 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11517 and fix it if it is affected.

What it is: CVE-2025-11517 is a high-severity vulnerability in stellarwp Event Tickets and Registration, published on 18 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11517 in the wild and no public exploit code.

Affected product: stellarwp Event Tickets and Registration. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11517/ (Markdown: https://insights.sbomify.com/CVE-2025-11517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11517
- OSV: https://osv.dev/vulnerability/CVE-2025-11517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11517/
Summaries are generated and may contain mistakes; the official description above is the record.