# CVE-2025-3499: Unauthenticated execution of arbitrary commands in Radiflow iSAP Smart Collector

> Unauthenticated attackers can execute arbitrary OS commands with administrative privileges via exposed REST APIs on Radiflow iSAP Smart Collector devices.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-jmx6-fwjr-crpx

## What is CVE-2025-3499?

CVE-2025-3499 is a critical command injection vulnerability in Radiflow iSAP Smart Collector, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The device has two web servers that expose unauthenticated REST APIs on the management network (TCP
ports 8084 and 8086). Exploiting OS command injection through these APIs, an attacker can send arbitrary
commands that are executed with administrative permissions by the underlying operating system.

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

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


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

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

## Is CVE-2025-3499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3499 is a critical command injection vulnerability in Radiflow iSAP Smart Collector, published on 9 Jul 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-3499 in the wild and no public exploit code.

Affected product: Radiflow iSAP Smart Collector. 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-3499/ (Markdown: https://insights.sbomify.com/CVE-2025-3499/index.md)
```

## Sources

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

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