Event Tickets with Ticket Scanner < 3.1.14 - Authenticated Ticket Data Disclosure and Removal via executeWCBackend
- Exploited
- No known exploitation
- Fix
- Fixed in 3.1.14
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.1.14.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.13% · 2nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Event Tickets with Ticket Scanner, a WordPress plugin, lets users with admin-area access view other customers' ticket codes and names and remove tickets from their orders, because it does not check that the user may manage WooCommerce orders. Exploitation requires the user to hold a role that an administrator has granted access to the plugin's admin area, which can be as low as Subscriber.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.2/10CVSS 4.2
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.1.14.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Event Tickets with Ticket Scanner
fixed in 3.1.14
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121857
Is CVE-2026-121857 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: cve.now feed data
Which versions are affected by CVE-2026-121857?
Event Tickets with Ticket Scanner: before 3.1.14.Source: cve.now feed data
How do I fix CVE-2026-121857?
Upgrade to a fixed version: 3.1.14.Source: cve.now feed data