# CVE-2025-15388: QNO Technology｜VPN Firewall - OS Command Injection

> Authenticated remote attackers can inject and execute arbitrary OS commands on QNO Technology VPN Firewalls.

- **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:** 31 Dec 2025
- **Updated:** 31 Dec 2025
- **Also known as:** GHSA-qx67-x2fg-4q4f

## What is CVE-2025-15388?

CVE-2025-15388 is a high-severity command injection vulnerability in QNO Technology VPN Firewall, published on 31 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VPN Firewall developed by QNO Technology has an OS Command Injection vulnerability, allowing authenticated remote attackers to inject arbitrary OS commands and execute them on the server.

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

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


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

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

## Is CVE-2025-15388 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15388 is a high-severity command injection vulnerability in QNO Technology VPN Firewall, published on 31 Dec 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-15388 in the wild and no public exploit code.

Affected product: QNO Technology VPN Firewall. 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-15388/ (Markdown: https://insights.sbomify.com/CVE-2025-15388/index.md)
```

## Sources

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

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