# CVE-2023-5653: WassUp Real Time Analytics <= 1.9.4.5 - Unauthenticated Stored XSS

> Unauthenticated attackers can inject malicious scripts via IP headers, leading to stored XSS attacks against logged-in administrators.

- **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:** 27 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4q47-vc82-p724

## What is CVE-2023-5653?

CVE-2023-5653 is a medium-severity cross-site scripting vulnerability in Unknown WassUp Real Time Analytics, published on 27 Nov 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 WassUp Real Time Analytics WordPress plugin through 1.9.4.5 does not escape IP address provided via some headers before outputting them back in an admin page, allowing unauthenticated users to perform Stored XSS attacks against logged in admins

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

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

It affects 1 product.


Products: Wassup Real Time Analytics Project Wassup Real Time Analytics.

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

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

## Is CVE-2023-5653 being exploited?

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

## Other vulnerabilities in Unknown WassUp Real Time Analytics

- [CVE-2016-10919](https://insights.sbomify.com/CVE-2016-10919/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5653 is a medium-severity cross-site scripting vulnerability in Unknown WassUp Real Time Analytics, published on 27 Nov 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: There is no known exploitation of CVE-2023-5653 in the wild and no public exploit code.

Affected product: Unknown WassUp Real Time Analytics. 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-5653/ (Markdown: https://insights.sbomify.com/CVE-2023-5653/index.md)
```

## Sources

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

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