# CVE-2026-7421: Passeum Ticketing <= 1.0 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'shop_name' Setting

> Administrators can inject malicious scripts via the shop_name setting, leading to stored XSS affecting all site visitors on pages using the plugin's shortcodes.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-4r7r-w926-gm5j

## What is CVE-2026-7421?

CVE-2026-7421 is a medium-severity cross-site scripting vulnerability in Passeum Ticketing, published on 2 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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 `get_shop_url()` method returning the `shop_name` setting value without sanitization when it begins with "http", combined with insufficient validation in the `validate_shop_name()` 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 `shop_name` to an attacker-controlled URL (e.g., `https://attacker.com`), which causes the plugin to enqueue external JavaScript and CSS from the attacker-controlled domain via `wp_register_script()` and `wp_register_style()`. 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 `unfiltered_html` capability.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-7421?


## How do I fix CVE-2026-7421?

No fix has been published for CVE-2026-7421 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7421 being exploited?

There is no known exploitation of CVE-2026-7421 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7421 and fix it if it is affected.

What it is: CVE-2026-7421 is a medium-severity cross-site scripting vulnerability in Passeum Ticketing, published on 2 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7421 in the wild and no public exploit code.

Affected product: Passeum Ticketing. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7421/ (Markdown: https://insights.sbomify.com/CVE-2026-7421/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7421
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7421
- OSV: https://osv.dev/vulnerability/CVE-2026-7421

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7421/
Summaries are generated and may contain mistakes; the official description above is the record.