CVE-2020-8985
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 · uneditedZendTo prior to 5.22-2 Beta allowed reflected XSS and CSRF via the unlock.tpl unlock user functionality.
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 confidenceZendTo versions prior to 5.22-2 Beta contain a reflected XSS vulnerability and a CSRF vulnerability in the unlock.tpl template's unlock user functionality. The reflected XSS allows attackers to inject malicious scripts via unsanitized user input that gets reflected in the response, while the CSRF flaw enables attackers to trick authenticated users into performing unintended actions like unlocking user accounts.
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= 3.10= 3.11= 3.12= 3.13= 3.20= 3.51= 3.52= 3.53= 3.54= 3.55= 3.56-2= 3.57CVSS 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.
-
Identify installed ZendTo versionCheck the version file or admin interface of your ZendTo installation. Common locations include a VERSION file in the root directory, the system information page in the admin panel, or the footer of web pages which often displays the version number.Affected if The installed version matches one of the affected versions: 3.10, 3.11, 3.12, 3.13, 3.20, 3.51, 3.52, 3.53, 3.54, 3.55, 3.56-2, or 3.57, or any version prior to 5.22-2 Beta.
-
Verify unlock user functionality is accessibleLocate the unlock.tpl template file in your ZendTo installation directory. Check if the unlock user functionality is exposed and accessible to authenticated users through the web interface, typically under the admin or user management section.Affected if The unlock.tpl template exists and the unlock user functionality is enabled and accessible in your environment.
-
Inspect unlock.tpl for input sanitizationOpen the unlock.tpl template file in your ZendTo installation and examine how user-supplied input (particularly any parameters used in the unlock process) is handled. Look for whether input is properly sanitized, escaped, or encoded before being reflected in the HTML response.Affected if User input in the unlock.tpl template is reflected in the response without proper sanitization or encoding, indicating the reflected XSS vulnerability is present.
-
Check for CSRF protection on unlock operationsReview the code handling the unlock user functionality, including both the frontend template and backend processing. Examine whether a valid CSRF token is required and validated for the unlock user action.Affected if The unlock user functionality does not implement CSRF token validation, allowing the CSRF vulnerability to exist.
You are affected if your ZendTo installation version is 3.10 through 3.57 (or any version prior to 5.22-2 Beta) and the unlock user functionality is accessible and lacks proper input sanitization and 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 dataUpgrade to ZendTo 5.22-2 Beta or later which contains the fix for these vulnerabilities. If immediate upgrade is not possible, implement input sanitization/encoding for the unlock user functionality and add CSRF tokens to all state-changing operations.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8985 — 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-8985 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