CVSS 3.1
4.2 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NCVE-2026-121857 Incorrect Authorization
Medium (4.2). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
The Event Tickets with Ticket Scanner WordPress plugin before 3.1.14 does not check that a user may manage WooCommerce orders before returning or removing ticket data for any order, allowing any role an administrator has granted access to the Event Tickets with Ticket Scanner WordPress plugin before 3.1.14's admin area (down to Subscriber) to view other customers' ticket codes and names and to remove tickets from their orders.
Severity
- EPSS
- 0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-863 Incorrect Authorization
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-121857 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121857?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121857?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121857 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-121857)
HTML:
<a href="https://cve.bz/cve/CVE-2026-121857"><img src="https://cve.bz/cve/badge/CVE-2026-121857.svg" alt="CVE-2026-121857"></a>
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.