CVE-2020-13819
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 · uneditedExtreme EAC Appliance 8.4.1.24 allows unauthenticated reflected XSS via a parameter in a GET request.
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 confidenceThe Extreme EAC Appliance version 8.4.1.24 contains a reflected cross-site scripting (XSS) vulnerability. An attacker can inject malicious JavaScript code through an unsanitized parameter in a GET request, which is then reflected back to the user without proper output encoding, allowing execution in the victim's browser context.
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< 8.5.0.169CVSS 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 Extreme Management Center versionLog into the Extreme Management Center web interface and navigate to the Help > About page, or access the CLI and run the command to display the system version (commonly 'show version' or similar).Affected if The displayed version is lower than 8.5.0.169 (for example, 8.4.1.24 as mentioned in the CVE summary).
-
Confirm web management interface is enabledVerify that the Extreme Management Center web service is running and accessible. This can be done by attempting to reach the web interface via HTTP/HTTPS or checking the service status via CLI.Affected if The web management interface is active and reachable, making the XSS attack vector viable.
-
Identify if the vulnerable parameter is presentReview HTTP request parameters in the application's GET endpoints. Since the CVE describes a reflected XSS through an unsanitized parameter, examine any user-controllable parameters in the URL that get reflected in the response without encoding.Affected if A parameter in a GET request accepts user input and reflects it back in the HTML response without proper sanitization or encoding.
You are affected if your Extreme Management Center version is below 8.5.0.169 and the web management interface is enabled, as the reflected XSS vulnerability exists in unsanitized GET request parameters.
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 data8.5.0.169
Implement proper input validation and output encoding for all user-supplied parameters in GET requests to prevent script injection. Apply context-specific encoding based on where the user input is rendered in the HTML response.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13819 — 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-2020-13819 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