# CVE-2022-4310: Slimstat Analytics < 4.9.3 - Unauthenticated Stored XSS

> Unauthenticated attackers can inject malicious scripts via URI logging, leading to code execution or account takeover when admins view logs.

- **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:** 9 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-r87w-g396-c68p

## What is CVE-2022-4310?

CVE-2022-4310 is a medium-severity cross-site scripting vulnerability in Unknown Slimstat Analytics, published on 9 Jan 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 Slimstat Analytics WordPress plugin before 4.9.3 does not sanitise and escape the URI when logging requests, which could allow unauthenticated attackers to perform Stored Cross-Site Scripting attacks against logged in admin viewing the logs

## Which versions are affected by CVE-2022-4310?

It affects 1 product.


Products: Wp-Slimstat Slimstat Analytics.

## How do I fix CVE-2022-4310?

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

## Is CVE-2022-4310 being exploited?

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

## Other vulnerabilities in Unknown Slimstat Analytics

- [CVE-2022-45373](https://insights.sbomify.com/CVE-2022-45373/): WordPress Slimstat Analytics Plugin <= 5.0.4 is vulnerable to SQL Injection (high 8.8)
- [CVE-2023-4598](https://insights.sbomify.com/CVE-2023-4598/): Slimstat Analytics <= 5.0.9 - Authenticated (Contributor+) Blind SQL Injection via Shortcode (high 8.8)
- [CVE-2023-0630](https://insights.sbomify.com/CVE-2023-0630/): Slimstat Analytics < 4.9.3.3 - Subscriber+ SQL Injection (high 8.8)
- [CVE-2024-9548](https://insights.sbomify.com/CVE-2024-9548/): Slimstat Analytics <= 5.2.6 - Unauthenticated Stored Cross-Site Scripting (high 7.2)
- [CVE-2022-45366](https://insights.sbomify.com/CVE-2022-45366/): WordPress Slimstat Analytics Plugin <= 5.0.4 is vulnerable to Cross Site Scripting (XSS) (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4310 and fix it if it is affected.

What it is: CVE-2022-4310 is a medium-severity cross-site scripting vulnerability in Unknown Slimstat Analytics, published on 9 Jan 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-2022-4310 exists.

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

## Sources

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

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