# CVE-2026-7176: Multiple vulnerabilities in Entradium by Crocantickets

> Attackers can inject JavaScript into event form fields, executing code on public ticket purchase pages for Entradium by Crocantickets users.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-24wv-pp5p-8868

## What is CVE-2026-7176?

CVE-2026-7176 is a medium-severity cross-site scripting vulnerability in Crocantickets Entradium, published on 1 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

CVE-2026-7176: the Help text and Title parameters in the endpoint /events/<event_name>-<event_city>/custom_form/edit during the process of creating or modifying forms associated with ticket sales for an event, which allows for the injection of JavaScript that will execute on the public ticket purchase page for the event.

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

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


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

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

## Is CVE-2026-7176 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7176 is a medium-severity cross-site scripting vulnerability in Crocantickets Entradium, published on 1 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-7176 in the wild and no public exploit code.

Affected product: Crocantickets Entradium. 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-7176/ (Markdown: https://insights.sbomify.com/CVE-2026-7176/index.md)
```

## Sources

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

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