CVE-2023-5880
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 · uneditedWhen the Genie Company Aladdin Connect garage door opener (Retrofit-Kit Model ALDCM) is placed into configuration mode the web servers “Garage Door Control Module Setup” page is vulnerable to XSS via a broadcast SSID name containing malicious code with client side Java Script and/or HTML. This allows the attacker to inject malicious code with client side Java Script and/or HTML into the users' web browser.
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 confidenceStored XSS vulnerability in the Genie Company Aladdin Connect garage door opener (ALDCM) web interface. When the device enters configuration mode, the 'Garage Door Control Module Setup' page renders the broadcast SSID name without proper sanitization, allowing injection of client-side JavaScript/HTML that executes in victim's browsers.
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<= 14.1.1CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check the installed firmware versionAccess the Aladdin Connect web interface and navigate to the device settings or status page to view the firmware version. This is typically found under a 'Device Info', 'About', or 'Settings' section in the web portal.Affected if The firmware version displayed is 14.1.1 or lower (any version <= 14.1.1).
-
Verify the device has a web interfaceConfirm that the garage door opener has an active web interface accessible via browser. This is typically accessed by connecting to the device's network or through the Aladdin Connect mobile app's web portal.Affected if The device has a web-based configuration interface.
-
Access the Garage Door Control Module Setup pagePlace the device into configuration mode and navigate to the 'Garage Door Control Module Setup' page in the web interface.Affected if The device enters configuration mode and displays the Setup page with the broadcast SSID field.
-
Inspect the SSID rendering for unsanitized outputView the page source or inspect the HTML element containing the broadcast SSID name. Check if the SSID value is rendered directly without HTML encoding (look for unescaped characters like <, >, ", or &).Affected if The SSID field displays raw, unescaped characters that could contain injected HTML or JavaScript tags.
A user is affected if their Aladdin Connect firmware version is 14.1.1 or lower AND they can access the configuration mode web interface where the broadcast SSID is displayed without proper sanitization.
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 dataThe vulnerability requires a vendor-supplied firmware update that implements proper input validation and output encoding for the SSID parameter on the setup page. Users should avoid placing the device in configuration mode on untrusted networks until the patch is applied.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5880 — 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-5880 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