# CVE-2025-41427: Command injection in WRC-X3000GS

> Remote authenticated attackers can execute arbitrary OS commands via the Connection Diagnostics page in ELECOM WRC-X3000GS series routers.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 25 Jun 2025
- **Also known as:** GHSA-7pgx-3wpq-wj9f

## What is CVE-2025-41427?

CVE-2025-41427 is a high-severity command injection vulnerability in ELECOM CO.,LTD. WRC-X3000GS, published on 24 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WRC-X3000GS, WRC-X3000GSA, and WRC-X3000GSN contain an improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability in Connection Diagnostics page. If a remote authenticated attacker sends a specially crafted request to the affected product, an arbitrary OS command may be executed.

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

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


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

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

## Is CVE-2025-41427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41427 is a high-severity command injection vulnerability in ELECOM CO.,LTD. WRC-X3000GS, published on 24 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41427 in the wild and no public exploit code.

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

## Sources

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

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