# CVE-2025-46272: Planet Technology Network Products OS Command Injection

> Unauthenticated attackers can execute arbitrary OS commands on Planet Technology network switches via command injection.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-89j9-cchw-j26m

## What is CVE-2025-46272?

CVE-2025-46272 is a critical command injection vulnerability in Planet Technology WGS-4215-8T2S, published on 24 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WGS-80HPT-V2 and WGS-4215-8T2S are vulnerable to a command injection 
attack that could allow an unauthenticated attacker to execute OS 
commands on the host system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-46272?


## How do I fix CVE-2025-46272?

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

## Is CVE-2025-46272 being exploited?

There is no known exploitation of CVE-2025-46272 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46272 and fix it if it is affected.

What it is: CVE-2025-46272 is a critical command injection vulnerability in Planet Technology WGS-4215-8T2S, published on 24 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46272 in the wild and no public exploit code.

Affected product: Planet Technology WGS-4215-8T2S. 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-2025-46272/ (Markdown: https://insights.sbomify.com/CVE-2025-46272/index.md)
```

## Sources

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

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