CVE-2020-10540
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 CSRF for certain combinations of rights and modules.
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 versions before 2020.9.6 contain a Cross-Site Request Forgery (CSRF) vulnerability affecting specific combinations of user rights and application modules. This allows attackers to induce authenticated users to perform unintended actions via malicious requests.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Locate WebUntis version numberAccess the WebUntis administration interface or check version information in the application's 'About' or 'System Info' section, or examine version files in the WebUntis installation directoryAffected if The displayed version is a number less than 2020.9.6 (e.g., 2020.9.5, 2020.8.x, etc.)
-
Identify active user rights configurationsReview user role configurations in the WebUntis admin panel under 'Users' or 'Rights Management' to determine which user types have elevated permissionsAffected if Users with elevated rights (such as administrators or teachers with extended privileges) are configured in the system
-
Determine which application modules are enabledCheck the WebUntis module configuration or feature flags in the admin settings to see which modules are active (e.g., timetable management, exam scheduling, substitution planning)Affected if Any of the modules that handle state-changing operations are enabled and accessible to authenticated users
-
Inspect for CSRF token implementationExamine the HTTP requests and form submissions in the WebUntis web interface using browser developer tools; check if state-changing actions include anti-CSRF tokens in request headers or form fieldsAffected if State-changing operations lack CSRF tokens or have predictable/non-unique token values, or no token validation is observed
You are affected if your WebUntis installation version is below 2020.9.6 AND you have authenticated users with elevated rights using modules that perform state-changing operations without CSRF protection.
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. Additionally, implement anti-CSRF tokens for state-changing operations in affected modules.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10540 — 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-10540 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