Skip to main content
Menu
CVEs

Liquid Web Event Tickets stored XSS in plugin-generated pages

WordPress Event Tickets plugin versions 5.31.1 and earlier are affected, by Liquid Web / StellarWP. The fix is version 5.31.1.1.

CVE-2026-131724Published , updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 5.31.1.1
Who is exposed
Specific setups only

Summary

The Event Tickets WordPress plugin from Liquid Web / StellarWP has a stored cross-site scripting flaw that lets an attacker store malicious script that runs in pages the plugin generates. An attacker can reach it remotely without logging in, but a user must take an action before the script runs.

Written by a model

Original description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Liquid Web / StellarWP Event Tickets event-tickets allows Stored XSS.This issue affects Event Tickets: from n/a through 5.31.1.

Who should check

Teams running the WordPress Event Tickets plugin version 5.31.1 or earlier on WordPress sites, including hosts and agencies managing them.

“Plugin <= 5.31.1 is vulnerable”

patchstack.com

What to do

  1. Check whether your setup matches what the bug needs.

    WordPress Event Tickets plugin version 5.31.1 or earlier
  2. Upgrade to a fixed version: 5.31.1.1.

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-131724 (WordPress Event Tickets plugin <= 5.31.1 - Cross Site Scripting (XSS) vulnerability), 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-131724 (entry last updated 2026-11-22):
Affected:
- Liquid Web / StellarWP Event Tickets: fixed in 5.31.1.1
Fixed versions: 5.31.1.1.
Conditions (all must be true for the bug to be hit):
- WordPress Event Tickets plugin version 5.31.1 or earlier (source: https://patchstack.com/database/wordpress/plugin/event-tickets/vulnerability/wordpress-event-tickets-plugin-5-31-1-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-131724 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131724 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://patchstack.com/database/wordpress/plugin/event-tickets/vulnerability/wordpress-event-tickets-plugin-5-31-1-cross-site-scripting-xss-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-131724
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-131724
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-131724"}.

Affected versions

cve.now Index

19Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

Questions about CVE-2026-131724

Is CVE-2026-131724 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

What does this mean?

This cross-site scripting flaw lets attackers inject malicious scripts into the site. Those scripts can steal visitor data or hijack visitor accounts.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-131724?

event-tickets: through 5.31.1 (fixed in 5.31.1.1).

Source: cve.now feed data

Am I affected, and how do I check?

The Event Tickets plugin by Liquid Web / StellarWP, at version 5.31.1 or earlier, is affected. The installed version appears on the Plugins page in the WordPress admin area.

Source: patchstack.com, cve.org

How do I fix CVE-2026-131724?

Update the Event Tickets plugin to version 5.31.1.1 or the latest available version.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.