CVE-2020-22453
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 · uneditedUntis WebUntis before 2020.9.6 allows XSS in multiple functions that store information.
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 confidenceUntis WebUntis before version 2020.9.6 contains a stored Cross-Site Scripting (XSS) vulnerability affecting multiple functions that persist user-provided information. Attackers can inject malicious JavaScript payloads through these storage functions, which then executes when other users view the contaminated data.
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< 2020.9.6CVSS 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 WebUntis installation versionLocate the WebUntis instance in your environment and determine its installed version number. This is typically found in the application header, about page, or server configuration files hosting the application.Affected if The installed version is any release prior to 2020.9.6 (for example, 2020.9.5, 2020.8.x, or earlier).
-
Confirm access to user input storage functionsWebUntis contains multiple functions that persist user-provided information, such as user profiles, custom fields, notes, or message boards. Determine which of these storage features are enabled and accessible to users in your deployment.Affected if Any storage function that accepts and persists user input is available to standard users or unauthenticated actors.
-
Examine stored data for suspicious script contentQuery the database or application storage where user-provided data is persisted. Look for patterns indicative of XSS payloads, such as <script> tags, javascript: URIs, event handler attributes (onclick, onload, etc.), or encoded variants.Affected if Any stored data contains unsanitized HTML, JavaScript, or script-like patterns that could execute in another user's browser.
Your environment is affected if the WebUntis version is below 2020.9.6 and users have access to storage functions that accept and display user-provided content without sanitization.
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 data2020.9.6
Upgrade to WebUntis version 2020.9.6 or later which contains the security patch. Until upgrade, consider restricting user permissions on affected functions and monitoring for malicious script patterns in stored data.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-22453 — 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-22453 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