# CVE-2023-47525: WordPress Event Management Tickets Booking Plugin <= 1.3.2 is vulnerable to Cross Site Scripting (XSS)

> Attackers can inject malicious scripts into the Event Monster WordPress plugin, potentially stealing user data or hijacking sessions.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-m4r9-8h98-x643

## What is CVE-2023-47525?

CVE-2023-47525 is a medium-severity cross-site scripting vulnerability in Event Monster – Event Management, Tickets Booking, Upcoming Event, published on 21 Dec 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in A WP Life Event Monster – Event Management, Tickets Booking, Upcoming Event allows Stored XSS.This issue affects Event Monster – Event Management, Tickets Booking, Upcoming Event: from n/a through 1.3.2.

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

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

It affects 1 product.


Products: Awplife Event Monster.

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

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

## Is CVE-2023-47525 being exploited?

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

## Other vulnerabilities in Event Monster – Event Management, Tickets Booking, Upcoming Event

- [CVE-2024-1895](https://insights.sbomify.com/CVE-2024-1895/): Event Monster <= 1.3.9 - Authenticated(Contributor+) PHP Object Injection via Custom Meta (high 7.5)
- [CVE-2022-3720](https://insights.sbomify.com/CVE-2022-3720/): Event Monster < 1.2.1 - Admin+ SQLi (high 7.2)
- [CVE-2024-11396](https://insights.sbomify.com/CVE-2024-11396/): Event monster <= 1.4.3 - Information Exposure Via Visitors List Export (medium 5.3)
- [CVE-2024-5059](https://insights.sbomify.com/CVE-2024-5059/): WordPress Event Monster Plugin <= 1.4.0 - Sensitive Data Exposure vulnerability (medium 5.3)
- [CVE-2022-3336](https://insights.sbomify.com/CVE-2022-3336/): Event Monster < 1.2.0 - Visitors Deletion via CSRF (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47525 is a medium-severity cross-site scripting vulnerability in Event Monster – Event Management, Tickets Booking, Upcoming Event, published on 21 Dec 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-47525 in the wild and no public exploit code.

Affected product: Event Monster – Event Management, Tickets Booking, Upcoming Event. 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-47525/ (Markdown: https://insights.sbomify.com/CVE-2023-47525/index.md)
```

## Sources

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

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