# CVE-2024-25641: Cacti RCE vulnerability when importing packages

> Authenticated users with import permissions can exploit path traversal in package imports to write arbitrary files, leading to remote code execution.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2024
- **Updated:** 4 Nov 2025
- **Also known as:** CLEANSTART-2024-UW33831, DEBIAN-CVE-2024-25641, GHSA-7cmj-g5qc-pj88, UBUNTU-CVE-2024-25641

## What is CVE-2024-25641?

CVE-2024-25641 is a critical path traversal vulnerability in Cacti Cacti, published on 13 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cacti provides an operational monitoring and fault management framework. Prior to version 1.2.27, an arbitrary file write vulnerability, exploitable through the "Package Import" feature, allows authenticated users having the "Import Templates" permission to execute arbitrary PHP code on the web server. The vulnerability is located within the `import_package()` function defined into the `/lib/import.php` script. The function blindly trusts the filename and file content provided within the XML data, and writes such files into the Cacti base path (or even outside, since path traversal sequences are not filtered). This can be exploited to write or overwrite arbitrary files on the web server, leading to execution of arbitrary PHP code or other security impacts. Version 1.2.27 contains a patch for this issue.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Cacti Cacti, Fedoraproject Fedora.

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

Upgrade to a fixed version.

## Is CVE-2024-25641 being exploited?

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

Public exploit code:

- CVE-2024-25641 - RCE Automated Exploit - Cacti 1.2.26 (github_poc): https://github.com/leo-mitch/CVE-2024-25641-RCE-Automated-Exploit-Cacti-1.2.26
- This repository automates the process of exploiting CVE-2024-25641 on Cacti 1.2.26 (github_poc): https://github.com/5ma1l/CVE-2024-25641
- Fully automated PoC - CVE-2024-25641 - RCE - Cacti < v1.2.26 🌵 (github_poc): https://github.com/StopThatTalace/CVE-2024-25641-CACTI-RCE-1.2.26
- PoC for CVE-2024-25641 Authenticated RCE on Cacti v1.2.26 (github_poc): https://github.com/Safarchand/CVE-2024-25641
- POC exploit for CVE-2024-25641 (github_poc): https://github.com/D3Ext/CVE-2024-25641
- https://github.com/regantemudo/CVE-2024-25641-Exploit-for-Cacti-1.2.26 (github_poc): https://github.com/regantemudo/CVE-2024-25641-Exploit-for-Cacti-1.2.26

## 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-2024-25641 and fix it if it is affected.

What it is: CVE-2024-25641 is a critical path traversal vulnerability in Cacti Cacti, published on 13 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25641 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-2024-25641/ (Markdown: https://insights.sbomify.com/CVE-2024-25641/index.md)
```

## Sources

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

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