CVE-2015-3976
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 (XSS) vulnerability in GE Multilink ML810/3000/3100 series switch 5.2.0 and earlier, and GE Multilink ML800/1200/1600/2400 4.2.1 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 confidenceCross-site scripting (XSS) vulnerability in the web management interface of GE Multilink ML800/1200/1600/2400 and ML810/3000/3100 series network switches. An attacker could inject malicious JavaScript through the web interface that executes in the browsers of authenticated users viewing the management console.
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= 5.2.0<= 5.2.0<= 5.2.0= 4.2.1= 4.2.1= 4.2.1= 4.2.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 switch modelLog into the switch CLI or check the physical device label to determine if the model is ML800, ML1200, ML1600, ML2400, ML810, ML3000, or ML3100Affected if Model is one of the listed affected models (ML800/1200/1600/2400 or ML810/3000/3100)
-
Check installed firmware versionUse the command to display firmware version (commonly 'show version' or 'show system-info' in the switch CLI), or log into the web management interface and check the firmware/version information pageAffected if Firmware version is 5.2.0 for ML810/3000/3100 series, or 4.2.1 for ML800/1200/1600/2400 series
-
Verify web management interface is enabledCheck the switch configuration for web management settings (commonly via 'show running-config' or 'show web' command), or attempt to access the web interface via HTTP/HTTPS on the switch IP addressAffected if Web management interface is enabled and accessible
User is affected if they have an ML800/1200/1600/2400 switch running firmware 4.2.1 or an ML810/3000/3100 switch running firmware 5.2.0 or below, AND the web management interface is enabled.
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 dataUpgrade switch firmware to a patched version beyond 5.2.0 (ML810/3000/3100 series) or 4.2.1 (ML800/1200/1600/2400 series). If no patched firmware is available, disable the web management interface and use CLI or SNMP-based management instead.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3976 — 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-2015-3976 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