dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-11517

HIGH · 7.5 CVSS v3.1 Published 2025-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Event Tickets and Registration WordPress plugin contains a payment bypass vulnerability in the /wp-json/tribe/tickets/v1/commerce/free/order REST API endpoint. The endpoint fails to validate whether a ticket type is actually free before processing orders, allowing unauthenticated attackers to obtain paid tickets without payment by manipulating the request to use the free order endpoint.

MitigationUpdate the Event Tickets and Registration plugin to version 5.26.6 or later to patch the missing validation in the free order endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Event Tickets and Registration plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Event Tickets and Registration' in the list
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    Click on the plugin name in the Plugins page to view version details, or inspect the plugin header in /wp-content/plugins/event-tickets/event-tickets.php for the Version field
    Affected if The version number is lower than the patched version (5.26.6)
  3. Check if the vulnerable REST API endpoint is accessible
    Send a GET request to /wp-json/tribe/tickets/v1/commerce/free/order using curl or a browser. A valid JSON response (even an error structure) indicates the endpoint exists and is reachable
    Affected if The endpoint returns a response without requiring authentication, meaning it is exposed to unauthenticated attackers
  4. Verify paid ticket types exist in the system
    In WordPress admin, navigate to Events > Tickets or Events > RSVP and review configured ticket types to see if any have a price greater than zero
    Affected if Paid ticket types are configured and could potentially be obtained without payment through the free order endpoint

The environment is affected if the Event Tickets and Registration plugin is installed with a version below 5.26.6, the free order REST API endpoint is accessible to unauthenticated users, and paid ticket types exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Event Tickets and Registration plugin to version 5.26.6 or later to patch the missing validation in the free order endpoint.

Recommended fix Moderate confidence

Event Tickets and Registration plugin version 5.27.0 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Event Tickets and Registration' (or 'Event Tickets' plugin)
  4. Check the current version number
  5. If the installed version is 5.26.5 or lower, update the plugin to the latest available version
  6. Verify the update completed successfully
  7. Test the /wp-json/tribe/tickets/v1/commerce/free/order endpoint behavior or confirm tickets still require payment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11517 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data