# CVE-2023-39362: Authenticated command injection in SNMP options of a Device

> An authenticated privileged user can achieve remote code execution on the server via command injection in SNMP options.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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:** 5 Sep 2023
- **Updated:** 27 Feb 2025
- **Also known as:** CLEANSTART-2024-HF66576, DEBIAN-CVE-2023-39362, GHSA-g6ff-58cj-x3cp, UBUNTU-CVE-2023-39362

## What is CVE-2023-39362?

CVE-2023-39362 is a high-severity command injection vulnerability in Cacti Cacti, published on 5 Sep 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cacti is an open source operational monitoring and fault management framework. In Cacti 1.2.24, under certain conditions, an authenticated privileged user, can use a malicious string in the SNMP options of a Device, performing command injection and obtaining remote code execution on the underlying server. The `lib/snmp.php` file has a set of functions, with similar behavior, that accept in input some variables and place them into an `exec` call without a proper escape or validation. 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-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 2 products.


Products: Cacti Cacti, Fedoraproject Fedora.

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

Upgrade to a fixed version.

## Is CVE-2023-39362 being exploited?

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

Public exploit code:

- https://github.com/jakabakos/CVE-2023-39362-cacti-snmp-command-injection-poc (github_poc): https://github.com/jakabakos/CVE-2023-39362-cacti-snmp-command-injection-poc
- WARNING: This is a vulnerable application to test the exploit for the Cacti command injection (CVE-2023-39362). Run it at your own risk! (github_poc): https://github.com/m3ssap0/cacti-rce-snmp-options-vulnerable-application
- Cacti 1.2.24 - Authenticated command injection when using SNMP options (exploitdb)

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

What it is: CVE-2023-39362 is a high-severity command injection vulnerability in Cacti Cacti, published on 5 Sep 2023. 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-2023-39362 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-39362/ (Markdown: https://insights.sbomify.com/CVE-2023-39362/index.md)
```

## Sources

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

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