# CVE-2025-2367: Oiwtech OIW-2431APGN-HP Personal Script Submenu formScript os command injection

> Remote attackers can execute arbitrary OS commands via the Personal Script Submenu in Oiwtech access points, leading to full system compromise.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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:** 17 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-mrvw-4m65-76p9

## What is CVE-2025-2367?

CVE-2025-2367 is a medium-severity command injection vulnerability in Oiwtech OIW-2431APGN-HP, published on 17 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in Oiwtech OIW-2431APGN-HP 2.5.3-B20131128 and classified as critical. This vulnerability affects unknown code of the file /boafrm/formScript of the component Personal Script Submenu. The manipulation leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2025-2367 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2367 is a medium-severity command injection vulnerability in Oiwtech OIW-2431APGN-HP, published on 17 Mar 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-2367 in the wild and no public exploit code.

Affected product: Oiwtech OIW-2431APGN-HP. 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-2367/ (Markdown: https://insights.sbomify.com/CVE-2025-2367/index.md)
```

## Sources

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

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