# CVE-2025-25053: Command injection in AC-PD-WPS-11ac

> Remote authenticated attackers can execute arbitrary OS commands via the web interface of Inaba Denki Wi-Fi access points.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 9 Apr 2025
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-m3h9-x8gr-vfvr

## What is CVE-2025-25053?

CVE-2025-25053 is a high-severity command injection vulnerability in Inaba Denki Sangyo Co., Ltd. AC-PD-WPS-11ac, published on 9 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OS command injection vulnerability in the WEB UI (the setting page) exists in Wi-Fi AP UNIT 'AC-WPS-11ac series'. If exploited, an arbitrary OS command may be executed by a remote attacker who can log in to the product.

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

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


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

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

## Is CVE-2025-25053 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25053 is a high-severity command injection vulnerability in Inaba Denki Sangyo Co., Ltd. AC-PD-WPS-11ac, published on 9 Apr 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-25053 in the wild and no public exploit code.

Affected product: Inaba Denki Sangyo Co., Ltd. AC-PD-WPS-11ac. 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-25053/ (Markdown: https://insights.sbomify.com/CVE-2025-25053/index.md)
```

## Sources

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

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