CVE-2025-27797
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 · uneditedOS command injection vulnerability in the specific service exists in Wi-Fi AP UNIT 'AC-WPS-11ac series'. If exploited, an arbitrary OS command may be executed by a remote attacker who can log in to the product.
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 · moderate confidenceOS command injection vulnerability in a specific service of the Wi-Fi AP UNIT AC-WPS-11ac series allows an authenticated remote attacker to execute arbitrary OS commands on the device through unsanitized input being passed to system calls.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 device modelAccess the device management interface or check the device label to confirm the exact model number is AC-WPS-11ac or related variants within the Wi-Fi AP UNIT AC-WPS-11ac seriesAffected if The device model is AC-WPS-11ac or a related variant from this product line
-
Locate firmware versionIn the device web interface or CLI, navigate to the system status or firmware information section to retrieve the currently installed firmware versionAffected if The installed firmware version has not been patched by the vendor and is older than any corrected release
-
Verify service accessibilityCheck the device configuration to determine if the vulnerable service (the specific service handling the unsanitized input) is exposed to the network and accessible from untrusted interfacesAffected if The service is enabled and reachable from external or untrusted networks rather than localhost only
-
Confirm authentication settingsReview the device authentication configuration to verify whether default credentials are in use or if weak authentication is configured for the management interfaceAffected if Default credentials remain unchanged or weak authentication is enabled, allowing attacker authentication
-
Inspect for compromise indicatorsReview system logs, running processes, or any unexpected scheduled tasks for signs of unauthorized command execution or unexpected network connectionsAffected if Logs show execution of unknown commands, unexpected processes, or connections from unrecognized sources
A user is affected if they operate an AC-WPS-11ac series device with an unpatched firmware version where the vulnerable service is network-accessible and the attacker can authenticate to the management interface.
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 dataApply vendor firmware patch when available; in the meantime, restrict network access to the device management interface to trusted IPs only and disable any unnecessary services.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27797 — 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-27797 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