# CVE-2024-30268: Cacti XSS vulnerability in display_settings

> Attackers can execute scripts to steal administrator cookies and hijack sessions in the Cacti monitoring framework.

- **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:** 13 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9m3v-whmr-pc2q, UBUNTU-CVE-2024-30268

## What is CVE-2024-30268?

CVE-2024-30268 is a medium-severity cross-site scripting vulnerability in cacti, published on 13 May 2024. 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

Cacti provides an operational monitoring and fault management framework. A reflected cross-site scripting vulnerability on the 1.3.x DEV branch allows attackers to obtain cookies of administrator and other users and fake their login using obtained cookies. This issue is fixed in commit a38b9046e9772612fda847b46308f9391a49891e.

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

## Which versions are affected by CVE-2024-30268?


## How do I fix CVE-2024-30268?

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

## Is CVE-2024-30268 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30268 and fix it if it is affected.

What it is: CVE-2024-30268 is a medium-severity cross-site scripting vulnerability in cacti, published on 13 May 2024. 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-2024-30268 exists.

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

## Sources

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

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