# CVE-2026-123129: Event Tickets Manager for WooCommerce 1.5.4 - 1.5.9 - Unauthenticated Site-wide Event Ticket Price Manipulation


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-gqcc-52m4-8mqh

## What is CVE-2026-123129?

CVE-2026-123129 is a medium-severity vulnerability in Unknown Event Tickets Manager for WooCommerce, published on 9 Nov 2026. 

### Official description

The Event Tickets Manager for WooCommerce WordPress plugin before 1.6.0 does not validate the ticket-type price sent to one of its unauthenticated AJAX actions when the referenced product has no ticket types configured, and stores the submitted price site-wide, where it is applied to the next event ticket added to any cart, allowing unauthenticated visitors to buy event tickets at an arbitrary price, including for free.

This is due to an incomplete fix of CVE-2026-34898.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-123129?


## How do I fix CVE-2026-123129?

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

## Is CVE-2026-123129 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123129 and fix it if it is affected.

What it is: CVE-2026-123129 is a medium-severity vulnerability in Unknown Event Tickets Manager for WooCommerce, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123129 in the wild and no public exploit code.

Affected product: Unknown Event Tickets Manager for WooCommerce. 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-2026-123129/ (Markdown: https://insights.sbomify.com/CVE-2026-123129/index.md)
```

## Sources

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

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