CVE-2023-28361
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 · uneditedA Cross-site WebSocket Hijacking (CSWSH) vulnerability found in UniFi OS 2.5 and earlier allows a malicious actor to access certain confidential information by persuading a UniFi OS user to visit a malicious webpage.Affected Products:Cloud Key Gen2Cloud Key Gen2 PlusUNVRUNVR ProfessionalUDMUDM ProfessionalUDM SEUDRMitigation:Update affected products to UniFi OS 3.0.13 or later.
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 confidenceCross-site WebSocket Hijacking (CSWSH) vulnerability in UniFi OS 2.5 and earlier allows attackers to hijack WebSocket connections by tricking authenticated users into visiting malicious webpages, enabling unauthorized access to confidential information due to improper origin validation in WebSocket handshake requests.
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< 3.0.13CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check UniFi OS versionLog into the UniFi OS controller web interface and navigate to Settings > System > About, or access the device via SSH and run 'ubnt-sysinfo' or check '/etc/version'Affected if The installed version is below 3.0.13 (e.g., 2.5.x, 2.4.x, or earlier)
-
Identify the device modelCheck the device label, packaging, or UniFi OS controller About page to confirm the model (Cloud Key Gen2, Cloud Key Gen2 Plus, UNVR, UDM, UDM Pro, UDM SE, or UDR)Affected if The device runs UniFi OS and the version cannot be verified as 3.0.13 or later
-
Determine network exposure of the UniFi OS WebUIReview firewall rules, port forwards, or NAT settings to check if port 443 or 8080 (UniFi OS web interface) is exposed directly to the internet or untrusted networksAffected if The UniFi OS management interface is reachable from outside the trusted local network without VPN or strict access controls
The environment is affected if the UniFi OS device runs version 2.5 or earlier (below 3.0.13), particularly when the management interface is accessible from networks where users could be tricked into visiting malicious webpages.
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.
dbcve · scoped3.0.13
Update all affected UniFi OS devices (Cloud Key Gen2, Cloud Key Gen2 Plus, UNVR, UDM, UDM Pro, UDM SE, UDR) to UniFi OS version 3.0.13 or later to remediate the vulnerability.
UniFi OS 3.0.13 or later
- 1. Identify the specific UniFi OS device model (Cloud Key Gen2, Cloud Key Gen2 Plus, UNVR, UDM, UDM SE, or UDR) that needs updating
- 2. Access the UniFi OS management console for the affected device
- 3. Navigate to System Settings > Firmware or check for updates in the device dashboard
- 4. Locate and apply the firmware update, ensuring the version is UniFi OS 3.0.13 or later
- 5. Verify the update was successful by confirming the new firmware version in the system information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28361 — 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-28361 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