CVE-2024-50376
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 CWE-79 "Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')" was discovered affecting the following devices manufactured by Advantech: EKI-6333AC-2G (<= 1.6.3), EKI-6333AC-2GD (<= v1.6.3) and EKI-6333AC-1GPO (<= v1.2.1). The vulnerability can be exploited remotely leveraging a rogue Wi-Fi access point with a malicious SSID.
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 confidenceThis is a stored XSS vulnerability in Advantech EKI-6333AC wireless devices where the Wi-Fi SSID is not properly sanitized before display. An attacker can deploy a rogue access point with a malicious SSID containing XSS payloads; when the device scans for or displays available networks, the payload executes in the web interface.
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.6.5< 1.6.5< 1.2.2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 model and variantLocate the device label or access the web interface to confirm the exact model number (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)Affected if The device is not one of these three variants, the check does not apply
-
Determine the installed firmware versionAccess the device web interface or check the firmware version via the admin console; compare the version number to the affected ranges (2G/2GD: < 1.6.5, 1GPO: < 1.2.2)Affected if The firmware version falls within the affected range for the specific model
-
Verify Wi-Fi functionality is enabledCheck the device wireless settings through the web interface or CLI to confirm Wi-Fi is activeAffected if Wi-Fi is disabled, the vulnerability cannot be triggered through normal device scanning
-
Inspect the available network list for suspicious SSIDsAccess the wireless network scan results or client list in the web interface; examine any SSIDs for unusual characters such as <, >, script tags, or encoded payloadsAffected if A stored XSS payload is present in any displayed SSID, indicating the device has processed a malicious beacon from a rogue access point
The device is affected if it is an EKI-6333AC variant with vulnerable firmware AND Wi-Fi scanning is enabled, particularly if anomalous SSIDs appear in the network list.
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 · scoped1.2.21.6.5
Apply vendor firmware updates to address the XSS vulnerability in SSID handling; until patches are available, disable Wi-Fi scanning features or use network segmentation to limit exposure to rogue access points.
Firmware 1.6.5 for EKI-6333AC-2G and EKI-6333AC-2GD; Firmware 1.2.2 for EKI-6333AC-1GPO
- 1. Identify the exact model number of the Advantech EKI device (EKI-6333AC-2G, EKI-6333AC-2GD, or EKI-6333AC-1GPO)
- 2. Check the current firmware version installed on the device through the web interface or CLI
- 3. Download the firmware update from the official Advantech support website (www.advantech.com) or contact Advantech directly for the patched firmware
- 4. Backup the current device configuration before performing the upgrade
- 5. Upload and install firmware version 1.6.5 for EKI-6333AC-2G or EKI-6333AC-2GD, or version 1.2.2 for EKI-6333AC-1GPO
- 6. Verify the firmware upgrade was successful by checking the new version number
- 7. Restore the device configuration if a backup was made
- 8. After upgrade, validate that the device is functioning normally and the web interface is accessible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50376 — 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-2024-50376 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