# CVE-2023-5238: EventPrime < 3.2.0 - Reflected HTML Injection on keyword parameter

> Attackers can inject malicious HTML into the search area via the keyword parameter, potentially executing scripts in victim browsers.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Oct 2023
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-g5gm-qgrx-3h7c

## What is CVE-2023-5238?

CVE-2023-5238 is a medium-severity cross-site scripting vulnerability in Unknown EventPrime, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The EventPrime WordPress plugin before 3.2.0 does not sanitise and escape a parameter before outputting it back in the page, leading to an HTML Injection on the plugin in the search area of the website.

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

## Which versions are affected by CVE-2023-5238?

It affects 1 product.


Products: Metagauss Eventprime.

## How do I fix CVE-2023-5238?

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

## Is CVE-2023-5238 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5238 exists.

## Other vulnerabilities in Unknown EventPrime

- [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-2024-12024](https://insights.sbomify.com/CVE-2024-12024/): Cross-site scripting in EventPrime – Events Calendar, Bookings and Tickets (high 7.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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5238 and fix it if it is affected.

What it is: CVE-2023-5238 is a medium-severity cross-site scripting vulnerability in Unknown EventPrime, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5238 exists.

Affected product: Unknown EventPrime. 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-2023-5238/ (Markdown: https://insights.sbomify.com/CVE-2023-5238/index.md)
```

## Sources

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

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