CVE-2023-31196
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 · uneditedMissing authentication for critical function in Wi-Fi AP UNIT allows a remote unauthenticated attacker to obtain sensitive information of the affected products. Affected products and versions are as follows: AC-PD-WAPU v1.05_B04 and earlier, AC-PD-WAPUM v1.05_B04 and earlier, AC-PD-WAPU-P v1.05_B04P and earlier, AC-PD-WAPUM-P v1.05_B04P and earlier, AC-WAPU-300 v1.00_B07 and earlier, AC-WAPUM-300 v1.00_B07 and earlier, AC-WAPU-300-P v1.00_B07 and earlier, and AC-WAPUM-300-P v1.00_B07 and earlier
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 confidenceMissing authentication for critical function in Wi-Fi AP UNIT allows remote unauthenticated attackers to obtain sensitive information from affected wireless access point products. The vulnerability exists in the web management interface or API where authentication is not enforced on sensitive endpoints.
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 data<= 1.05_b04<= 1.05_b04<= 1.05_b04p<= 1.05_b04p<= 1.00_b07<= 1.00_b07<= 1.00_b07<= 1.00_b07CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web management interface or use SNMP/CLI to retrieve the product name and model number. Look for identifiers such as AC-PD-WAPU, AC-PD-WAPUM, AC-WAPU-300, or AC-WAPUM-300 in the system information or device status page.Affected if The device model is one of the following: Inaba Ac Pd Wapu, Inaba Ac Pd Wapum, Inaba Ac Pd Wapu P, Inaba Ac Pd Wapum P, Inaba Ac Wapu 300, Inaba Ac Wapum 300, Inaba Ac Wapum 300 P, or Inaba Ac Wapu 300 P.
-
Check the installed firmware versionNavigate to the web management interface system settings, firmware upgrade page, or device status section. Alternatively, access the device via CLI and use commands such as 'show version' or 'firmware version' to retrieve the current firmware build.Affected if The firmware version is at or below 1.05_b04 for AC-PD-WAPU/UM models, at or below 1.05_b04p for AC-PD-WAPU/UM-P models, or at or below 1.00_b07 for AC-WAPU-300/WAPUM-300 models.
-
Verify web management interface accessibilityAttempt to access the device's web management interface from a remote location without providing credentials. Use a web browser or HTTP client to send requests to common management endpoints such as /, /admin, /api, or /status.Affected if Sensitive endpoints return valid HTTP responses with device information, configuration data, or system status without requiring login credentials.
-
Inspect API endpoint authenticationSend HTTP requests to API endpoints on the device (such as /api/status, /api/config, or /api/system) using tools like curl or Burp Suite, without including authentication headers or session cookies.Affected if The API returns sensitive information (device configuration, wireless settings, client data, or system details) without enforcing authentication.
The device is affected if it is an Inaba AC-PD-WAPU/UM or AC-WAPU-300/WAPUM-300 model running firmware at or below the affected versions AND the web management interface or API exposes sensitive endpoints without requiring authentication.
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 dataUpdate affected devices to firmware versions v1.05_B04P or later for AC-PD-WAPU/UM models, and v1.00_B07 or later for AC-WAPU-300 models. If patching is not immediately possible, restrict network access to management interfaces via firewall rules or VLAN segmentation.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31196 — 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-2023-31196 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