CVE-2025-32458
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 · uneditedThe Quantenna Wi-Fi chipset ships with a local control script, router_command.sh (in the get_syslog_from_qtn argument), that is vulnerable to command injection. This is an instance of CWE-88, "Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')," and is estimated as a CVSS 7.7 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). This issue affects Quantenna Wi-Fi chipset through version 8.0.0.28 of the latest SDK, and appears to be unpatched at the time of this CVE record's first publishing, though the vendor has released a best practices guide for implementors of this chipset.
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 confidenceThe Quantenna Wi-Fi chipset includes a local control script (router_command.sh) vulnerable to argument injection in the get_syslog_from_qtn argument. An attacker with local access to the device can inject arbitrary commands through improper neutralization of argument delimiters, achieving high confidentiality and integrity impact despite no availability impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Wi-Fi chipset vendorCheck your device documentation or examine the hardware/components to determine if it uses an Onsemi Quantenna Wi-Fi chipset (QCS Ax2, QCS Ax3, QHS710, QSR10ga, QSR10gu, or QD840)Affected if The device contains an Onsemi Quantenna chipset from the affected product list
-
Locate the router_command.sh scriptSearch for the file named 'router_command.sh' in the device firmware or filesystem - this is typically found in system binary or script directoriesAffected if The router_command.sh script exists on the device
-
Verify get_syslog_from_qtn argument is presentExamine the router_command.sh script to confirm it accepts a 'get_syslog_from_qtn' argument or parameterAffected if The script contains handling for the get_syslog_from_qtn argument
-
Test for argument injection vulnerabilityWith local access, invoke the script with the get_syslog_from_qtn argument followed by shell metacharacters (such as ;ls or $(whoami)) to determine if arbitrary command execution occursAffected if Arbitrary commands are executed when special characters are injected into the get_syslog_from_qtn argument
Your environment is affected if you have a device using any Onsemi Quantenna chipset firmware (QCS Ax2, QCS Ax3, QHS710, QSR10ga, QSR10gu, or QD840) that contains the vulnerable router_command.sh script with the get_syslog_from_qtn argument, as all firmware versions for these products are affected.
Generated from the published advisory. Verify against your own configuration.
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 dataUntil an official vendor patch is available, restrict local access to the device and implement input validation on any wrapper scripts calling router_command.sh. Consider network segmentation to limit exposure from compromised local accounts.
- Consultation5.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32458 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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