dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-43978

HIGH · 7.4 CVSS v3.1 Published 2025-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jointelli 5G CPE 21H01 firmware JY_21H01_A3_v1.36 contains multiple blind OS command injection vulnerabilities in the web interface (ubus). Authenticated attackers can inject arbitrary OS commands through SSID, WPS, Traceroute, and Ping parameters via endpoints like /ubus/?flag=set_WPS_pin, /ubus/?flag=netAppStar1, and /ubus/?flag=set_wifi_cfgs, achieving root-level code execution.

MitigationApply vendor firmware patch if available; otherwise, restrict access to the web management interface via firewall rules, implement network segmentation to isolate the CPE, and disable remote management access from untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify firmware version
    Access the device's web management interface and navigate to the status or system information page to view the firmware version. Alternatively, check via CLI if accessible: 'cat /proc/version' or ' firmwareutil get version'. Compare the displayed version to 'JY_21H01_A3_v1.36'.
    Affected if The device runs firmware version JY_21H01_A3_v1.36 or an earlier version before any vendor patch.
  2. Confirm web interface is accessible
    Attempt to reach the device's web interface from a test system using HTTP or HTTPS to the device's management IP address. Verify the ubus endpoint responds: send a request to 'http://<device_ip>/ubus/'.
    Affected if The web management interface (ubus) is exposed and reachable on the network.
  3. Check authentication configuration
    Inspect the device's web management settings to determine if authentication is enabled for the ubus interface. Look for user accounts configured for web access and verify login functionality works.
    Affected if Default or custom authentication credentials are configured and allow access to the web interface.
  4. Verify vulnerable endpoint parameters exist
    Examine the web interface for availability of WPS, SSID, Ping, or Traceroute configuration features. These correspond to the flags 'set_WPS_pin', 'netAppStar1', 'set_wifi_cfgs' used with the /ubus/ endpoint.
    Affected if The WPS, SSID configuration, Ping, or Traceroute features are accessible through the web interface.
  5. Inspect for indicators of compromise
    Review device system logs for unexpected commands, unusual network connections, or unauthorized configuration changes. Check for new user accounts or modified scripts in /etc/ or /var/ directories.
    Affected if Log entries show unexpected command execution, or system files show unauthorized modifications consistent with injected commands.

A user is affected if the Jointelli 5G CPE runs the JY_21H01_A3_v1.36 firmware, has the web management interface accessible on the network, and allows authenticated access to WPS, SSID, Ping, or Traceroute configuration features via the ubus endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch if available; otherwise, restrict access to the web management interface via firewall rules, implement network segmentation to isolate the CPE, and disable remote management access from untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43978 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43978 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data