CVE-2020-25902
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 · uneditedBlackboard Collaborate Ultra 20.02 is affected by a cross-site scripting (XSS) vulnerability. The XSS payload will execute on the class room, which leads to stealing cookies from users who join the class. NOTE: Third-parties dispute the validity of this entry as a possible false positive during research
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 · low confidenceBlackboard Collaborate Ultra 20.02 contains a cross-site scripting (XSS) vulnerability where malicious payloads execute within the classroom context, enabling attackers to steal user cookies and potentially hijack sessions. The CVSS 6.1 suggests a relatively straightforward XSS attack requiring some user interaction.
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= 20.02CVSS 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 your Blackboard Collaborate Ultra versionLog into your Blackboard Collaborate Ultra portal and navigate to the Settings or About section, typically found under the profile menu or in the browser-based classroom interface. Look for a version number displayed in the application footer or in the session information panel.Affected if The displayed version is exactly 20.02 (no other versions are listed as affected by this CVE).
-
Check browser developer tools for version metadataOpen your browser's developer tools (F12), go to the Network tab, and load the Blackboard Collaborate Ultra session page. Inspect the initial page load response or any JavaScript files for a version string that may be hardcoded in the client-side code.Affected if The version string in the response matches 20.02 specifically.
-
Review integration or admin configurationIf your organization uses Blackboard Learn integration or an admin panel to launch Collaborate Ultra sessions, check any configuration pages that display the Collaborate product version. This may be found in the course management area or integration settings.Affected if The configured Collaborate version is listed as 20.02.
Your environment is affected only if the Blackboard Collaborate Ultra version in use is exactly 20.02, as this is the sole version listed as vulnerable to this XSS flaw.
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 dataSince this is a third-party SaaS platform, organizations should report the issue to Blackboard and monitor for vendor patches; implement Content Security Policy headers as a defense-in-depth measure while awaiting remediation.
- Consultation2.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 $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25902 — 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-25902 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