# CVE-2025-53472: Command injection in WRC-BE36QS-B

> Remote authenticated attackers can execute arbitrary OS commands via the WebGUI of ELECOM wireless routers.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-p7jm-pv37-vmrp

## What is CVE-2025-53472?

CVE-2025-53472 is a high-severity command injection vulnerability in ELECOM CO.,LTD. WRC-BE36QS-B, published on 22 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

WRC-BE36QS-B and WRC-W701-B contain an improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability in WebGUI. If exploited, an arbitrary OS command may be executed by a remote attacker who can log in to WebGUI.

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

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


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

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

## Is CVE-2025-53472 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53472 is a high-severity command injection vulnerability in ELECOM CO.,LTD. WRC-BE36QS-B, published on 22 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53472 in the wild and no public exploit code.

Affected product: ELECOM CO.,LTD. WRC-BE36QS-B. 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-53472/ (Markdown: https://insights.sbomify.com/CVE-2025-53472/index.md)
```

## Sources

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

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