# CVE-2023-39510: Stored Cross-site Scripting in reports_admin.php through Device-Name in 'select' input in Cacti

> An authenticated user can inject malicious JavaScript via device names, leading to stored XSS attacks against administrators viewing reports.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **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:** Yes
- **Published:** 5 Sep 2023
- **Updated:** 13 Feb 2025
- **Also known as:** CLEANSTART-2024-SX62684, DEBIAN-CVE-2023-39510, GHSA-24w4-4hp2-3j8h, UBUNTU-CVE-2023-39510

## What is CVE-2023-39510?

CVE-2023-39510 is a medium-severity cross-site scripting vulnerability in Cacti Cacti, published on 5 Sep 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cacti is an open source operational monitoring and fault management framework. Affected versions are subject to a Stored Cross-Site-Scripting (XSS) Vulnerability allows an authenticated user to poison data stored in the _cacti_'s database. These data will be viewed by administrative _cacti_ accounts and execute JavaScript code in the victim's browser at view-time. The`reports_admin.php` script displays reporting information about graphs, devices, data sources etc.
CENSUS found that an adversary that is able to configure a malicious Device name, can deploy a stored XSS attack against any user of the same (or broader) privileges. A user that possesses the _General Administration>Sites/Devices/Data_ permissions can configure the device names in _cacti_. This configuration occurs through `http://<HOST>/cacti/host.php`, while the rendered malicious payload is exhibited at `http://<HOST>/cacti/reports_admin.php` when the a graph with the maliciously altered device name is linked to the report. This vulnerability has been addressed in version 1.2.25. Users are advised to upgrade. Users unable to update should manually filter HTML output.

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

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

It affects 2 products.


Products: Cacti Cacti, Fedoraproject Fedora.

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

Upgrade to a fixed version.

## Is CVE-2023-39510 being exploited?

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

## Other vulnerabilities in Cacti Cacti

- [CVE-2022-46169](https://insights.sbomify.com/CVE-2022-46169/): Cacti Command Injection (critical 9.8, exploited in the wild)
- [CVE-2026-39893](https://insights.sbomify.com/CVE-2026-39893/): Cacti: Pre-authentication SQL injection via rfilter RLIKE clause in graph_view.php (critical 9.8)
- [CVE-2026-39938](https://insights.sbomify.com/CVE-2026-39938/): Cacti: Unauthenticated RCE on Graph Image (critical 9.8)
- [CVE-2026-39955](https://insights.sbomify.com/CVE-2026-39955/): Cacti has Pre-Authentication SQL Injection via unanchored FILTER_VALIDATE_REGEXP in graph_view.php (critical 9.8)
- [CVE-2023-39361](https://insights.sbomify.com/CVE-2023-39361/): Unauthenticated SQL Injection in graph_view.php in Cacti (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39510 is a medium-severity cross-site scripting vulnerability in Cacti Cacti, published on 5 Sep 2023. An attacker needs administrator access to exploit it, 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-39510 exists.

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

## Sources

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

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