CVE-2024-42412
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 · uneditedCross-site scripting vulnerability exists in ELECOM wireless access points due to improper processing of input values in menu.cgi. If a user views a malicious web page while logged in to the product, an arbitrary script may be executed on the user's 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 confidenceCross-site scripting (XSS) vulnerability in ELECOM wireless access points allows execution of arbitrary JavaScript in the context of an authenticated user's browser via improper input validation in menu.cgi. The attack requires the victim to be logged in and view a malicious page, making it a stored or reflected XSS that leverages the authenticated session.
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.5.6<= 1.5.10CVSS 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
- None
CVSS:3.1/AV:N/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 modelAccess the device's web management interface or check the device label to confirm the model is Elecom Wab S1167 Ps or Wab I1750 PsAffected if Model is Elecom Wab S1167 Ps or Wab I1750 Ps
-
Check the firmware versionLog into the web interface and navigate to the status or system information page to view the installed firmware version. Compare against the affected ranges: <= 1.5.6 for Wab S1167 Ps, <= 1.5.10 for Wab I1750 PsAffected if Firmware version is at or below 1.5.6 for Wab S1167 Ps, or at or below 1.5.10 for Wab I1750 Ps
-
Verify the web interface is accessibleAttempt to access menu.cgi on the device (typically http://[device-ip]/menu.cgi) in a web browserAffected if The menu.cgi endpoint is reachable and responds to requests
-
Confirm authentication is configuredCheck if the device has login authentication enabled for the web management interface, or if default/admin credentials are in useAffected if The device web interface accepts authenticated sessions, as the XSS requires an authenticated context to trigger
If the device is an Elecom Wab S1167 Ps or Wab I1750 Ps with firmware at or below the affected version and the web management interface is accessible with authentication enabled, the environment is vulnerable to CVE-2024-42412.
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 dataImplement proper input sanitization and output encoding in menu.cgi to neutralize malicious script payloads. Consider implementing Content Security Policy headers as defense-in-depth.
- 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-2024-42412 — 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-42412 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