# CVE-2019-25487: SAPIDO RB-1732 V2.0.43 Remote Command Execution via formSysCmd

> Unauthenticated attackers can execute arbitrary system commands on SAPIDO RB-1732 routers via the formSysCmd endpoint.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 11 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-c925-88rr-2hq4

## What is CVE-2019-25487?

CVE-2019-25487 is a critical command injection vulnerability in Sapido RB-1732, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAPIDO RB-1732 V2.0.43 contains a remote command execution vulnerability that allows unauthenticated attackers to execute arbitrary system commands by submitting malicious input to the formSysCmd endpoint. Attackers can send POST requests with the sysCmd parameter containing shell commands to execute code on the device with router privileges.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2019-25487?


## How do I fix CVE-2019-25487?

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

## Is CVE-2019-25487 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25487 and fix it if it is affected.

What it is: CVE-2019-25487 is a critical command injection vulnerability in Sapido RB-1732, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25487 exists.

Affected product: Sapido RB-1732. 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-2019-25487/ (Markdown: https://insights.sbomify.com/CVE-2019-25487/index.md)
```

## Sources

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

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