Vulnerabilities

Vulnerability · CVE-2026-7421

The Passeum Ticketing plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.0.

Published Jun 3, 2026 · catalog updated Jul 21, 2026 · The Passeum Ticketing plugin

Check if you run it

No confirmed exploitation is on record for CVE-2026-7421. EPSS is 0.33%. Act only if a listed version of The Passeum Ticketing plugin is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The Passeum Ticketing plugin).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.33%
Remediation
Version ranges on file
Affected products
stated named in the record

The Passeum Ticketing plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.0. This is due to the method returning the setting value without sanitization when it begins with "http", combined with insufficient validation in the function which only checks for empty values and string type. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary external scripts by setting the to an attacker-controlled URL (e.g., ), which causes the plugin to enqueue external JavaScript and CSS from the attacker-controlled domain via and . The injected scripts execute on every frontend page containing any Passeum Ticketing shortcode, affecting all site visitors. Please note that this does not affect single-site installations as administrators already have the capability.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated named in the record<= 1.0

How to fix CVE-2026-7421

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-7421. EPSS is 0.33%. Act only if a listed version of The Passeum Ticketing plugin is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 1.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-79: Cross-site Scripting (XSS). EPSS 0.33%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 3, 2026 · NIST NVD

    Detected

    The Passeum Ticketing plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.0. This is due to the method returning the setting value without sanitization when it begins with "http", combined with insufficient validation in the function which only checks for empty values and string type. This makes it possible for authenticated attackers, with Adm

  2. Jul 21, 2026 · NIST NVD

    Updated

    The Passeum Ticketing plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.0. This is due to the method returning the setting value without sanitization when it begins with "http", combined with insufficient validation in the function which only checks for empty values and string type. This makes it possible for authenticated attackers, with Adm

Sources

  • CVE.orgVulnerability recordCVE-2026-7421

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-7421

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-7421

    The Passeum Ticketing plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.0. This is due to the method returning the setting value without sanitization when it begins with "http", combined with ins

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.