# CVE-2024-12024: Cross-site scripting in EventPrime – Events Calendar, Bookings and Tickets

> Unauthenticated attackers can inject scripts via ticket fields, executing them in admin sessions if guest submissions are enabled.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wqfp-fvw2-67qm

## What is CVE-2024-12024?

CVE-2024-12024 is a high-severity cross-site scripting vulnerability in metagauss EventPrime – Events Calendar, Bookings and Tickets, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The EventPrime – Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the em_ticket_category_data and em_ticket_individual_data parameters in all versions up to, and including, 4.0.7.3 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 an administrative user accesses an injected page.
Note: this vulnerability requires the "Guest Submissions" setting to be enabled. It is disabled by default.

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

## Which versions are affected by CVE-2024-12024?

It affects 1 product.


Products: Metagauss Eventprime.

## How do I fix CVE-2024-12024?

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

## Is CVE-2024-12024 being exploited?

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

## Other vulnerabilities in metagauss EventPrime – Events Calendar, Bookings and Tickets

- [CVE-2024-31275](https://insights.sbomify.com/CVE-2024-31275/): WordPress EventPrime plugin <= 3.3.4 - Booking Price Manipulation vulnerability (high 8.2)
- [CVE-2024-24832](https://insights.sbomify.com/CVE-2024-24832/): WordPress EventPrime plugin <= 3.3.9 - Broken Access Control vulnerability (high 8.2)
- [CVE-2023-45637](https://insights.sbomify.com/CVE-2023-45637/): WordPress EventPrime Plugin <= 3.1.5 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2023-35884](https://insights.sbomify.com/CVE-2023-35884/): WordPress EventPrime Plugin <= 3.0.5 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2023-33326](https://insights.sbomify.com/CVE-2023-33326/): WordPress EventPrime Plugin <= 2.8.6 is vulnerable to Cross Site Scripting (XSS) (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12024 and fix it if it is affected.

What it is: CVE-2024-12024 is a high-severity cross-site scripting vulnerability in metagauss EventPrime – Events Calendar, Bookings and Tickets, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12024 in the wild and no public exploit code.

Affected product: metagauss EventPrime – Events Calendar, Bookings and Tickets. 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-2024-12024/ (Markdown: https://insights.sbomify.com/CVE-2024-12024/index.md)
```

## Sources

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

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