# CVE-2025-5145: Netcore POWER13 Query String cgi-bin command injection

> Remote attackers can execute arbitrary commands via the query string handler in Netcore routers, requiring immediate attention from network administrators.

- **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/E:P`)
- **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:** 25 May 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-wwr5-99rv-v9gv

## What is CVE-2025-5145?

CVE-2025-5145 is a medium-severity command injection vulnerability in Netcore B6V2, published on 25 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in Netcore NBR1005GPEV2, B6V2, COVER5, NAP830, NAP930, NBR100V2, NBR200V2 and POWER13 up to 20250508. This affects an unknown part of the file /www/cgi-bin/ of the component Query String Handler. The manipulation leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2025-5145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5145 is a medium-severity command injection vulnerability in Netcore B6V2, published on 25 May 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-5145 in the wild and no public exploit code.

Affected product: Netcore B6V2. 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-5145/ (Markdown: https://insights.sbomify.com/CVE-2025-5145/index.md)
```

## Sources

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

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