# CVE-2025-43978: Command injection in n/a

> Authenticated attackers can execute arbitrary OS commands with root privileges via crafted inputs in Jointelli 5G CPE firmware.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 5 Aug 2025
- **Also known as:** GHSA-46fj-mvqm-297p

## What is CVE-2025-43978?

CVE-2025-43978 is a high-severity command injection vulnerability in n/a, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jointelli 5G CPE 21H01 firmware JY_21H01_A3_v1.36 devices allow (blind) OS command injection. Multiple endpoints are vulnerable, including /ubus/?flag=set_WPS_pin and /ubus/?flag=netAppStar1 and /ubus/?flag=set_wifi_cfgs. This allows an authenticated attacker to execute arbitrary OS commands with root privileges via crafted inputs to the SSID, WPS, Traceroute, and Ping fields.

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

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


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

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

## Is CVE-2025-43978 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-43978 is a high-severity command injection vulnerability in n/a, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-43978 in the wild and no public exploit code.

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

## Sources

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

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