CVE
Event Tickets with Ticket Scanner unauthenticated stored XSS via 'code' parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Event Tickets with Ticket Scanner plugin for WordPress has a stored cross-site scripting flaw in its 'code' parameter. Remotely, without logging in, an attacker can inject scripts that run in a user's browser whenever that user opens the affected page.
Original description
The Event Tickets with Ticket Scanner plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'code' parameter in all versions up to, and including, 3.3.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload persists through WooCommerce session data into order-item metadata and executes when rendered in the ticket scanner interface.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-111825 (Event Tickets with Ticket Scanner <= 3.3.1 - Unauthenticated Stored Cross-Site Scripting via 'code' Parameter), 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-111825 (entry last updated 2026-11-18):
Affected:
- sasonikolov Event Tickets with Ticket Scanner: through 3.3.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-111825 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111825 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:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f7d6bd1b-e072-43b6-a72e-6c0758d62da1?source=cve
- https://plugins.trac.wordpress.org/browser/event-tickets-with-ticket-scanner/tags/3.2.7/ticket_scanner.js#L1749
- https://plugins.trac.wordpress.org/browser/event-tickets-with-ticket-scanner/tags/3.2.7/ticket_scanner.js#L1855
- https://plugins.trac.wordpress.org/browser/event-tickets-with-ticket-scanner/tags/3.2.7/includes/woocommerce/class-frontend.php#L441
- https://plugins.trac.wordpress.org/browser/event-tickets-with-ticket-scanner/tags/3.2.7/includes/woocommerce/class-frontend.php#L425
- https://plugins.trac.wordpress.org/browser/event-tickets-with-ticket-scanner/tags/3.2.7/sasoEventtickets_AdminSettings.php#L3054
- https://plugins.trac.wordpress.org/changeset/3784611/
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-111825
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-111825"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- sasonikolov Event Tickets with Ticket Scanner
through 3.3.1
Evidence 10
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111825
Is CVE-2026-111825 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-111825?
Event Tickets with Ticket Scanner: through 3.3.1.Source: cve.now feed data