# CVE-2023-30534: Insecure Deserialization in Cacti

> Attackers could potentially execute arbitrary code via insecure deserialization in Cacti, though current gadget chains were not exploitable.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2023
- **Updated:** 13 Feb 2025
- **Also known as:** CLEANSTART-2024-VJ51383, DEBIAN-CVE-2023-30534, GHSA-77rf-774j-6h3p, UBUNTU-CVE-2023-30534

## What is CVE-2023-30534?

CVE-2023-30534 is a medium-severity unsafe deserialization vulnerability in Cacti Cacti, published on 5 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cacti is an open source operational monitoring and fault management framework. There are two instances of insecure deserialization in Cacti version 1.2.24. While a viable gadget chain exists in Cacti’s vendor directory (phpseclib), the necessary gadgets are not included, making them inaccessible and the insecure deserializations not exploitable. Each instance of insecure deserialization is due to using the unserialize function without sanitizing the user input. Cacti has a “safe” deserialization that attempts to sanitize the content and check for specific values before calling unserialize, but it isn’t used in these instances. The vulnerable code lies in graphs_new.php, specifically within the host_new_graphs_save function. This issue has been addressed in version 1.2.25. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 2 products.


Products: Cacti Cacti, Fedoraproject Fedora.

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

Upgrade to a fixed version.

## Is CVE-2023-30534 being exploited?

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

Public exploit code:

- Cacti < 1.2.25 Insecure Deserialization (nuclei): http/cves/2023/CVE-2023-30534.yaml

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

What it is: CVE-2023-30534 is a medium-severity unsafe deserialization vulnerability in Cacti Cacti, published on 5 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30534 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-30534/ (Markdown: https://insights.sbomify.com/CVE-2023-30534/index.md)
```

## Sources

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

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