# CVE-2025-23407: Privilege escalation in AC-PD-WPS-11ac

> A remote attacker with login access can escalate privileges to modify settings on Inaba Denki Wi-Fi access points due to incorrect privilege assignment.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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:** 9 Apr 2025
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-xfj2-q583-73rv

## What is CVE-2025-23407?

CVE-2025-23407 is a medium-severity 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

Incorrect privilege assignment vulnerability in the WEB UI (the setting page) exists in Wi-Fi AP UNIT 'AC-WPS-11ac series'. If exploited, a remote attacker who can log in to the product may alter the settings without appropriate privileges.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-23407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23407 is a medium-severity 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-23407 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-23407/ (Markdown: https://insights.sbomify.com/CVE-2025-23407/index.md)
```

## Sources

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

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