CVE-2020-5575
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 · uneditedCross-site scripting vulnerability in Movable Type series (Movable Type 7 r.4606 (7.2.1) and earlier (Movable Type 7), Movable Type Advanced 7 r.4606 (7.2.1) and earlier (Movable Type Advanced 7), Movable Type for AWS 7 r.4606 (7.2.1) and earlier (Movable Type for AWS 7), Movable Type 6.5.3 and earlier (Movable Type 6.5), Movable Type Advanced 6.5.3 and earlier (Movable Type Advanced 6.5), Movable Type 6.3.11 and earlier (Movable Type 6.3), Movable Type Advanced 6.3.11 and earlier (Movable Type 6.3), Movable Type Premium 1.29 and earlier, and Movable Type Premium Advanced 1.29 and earlier) allows remote attackers to inject arbitrary script or HTML via unspecified vectors.
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 confidenceCross-site scripting (XSS) vulnerability in Movable Type CMS allows remote attackers to inject arbitrary JavaScript or HTML via unspecified vectors. The vulnerability stems from insufficient input sanitization or output encoding in the affected Movable Type components, enabling malicious scripts to be executed in the context of authenticated users' browsers.
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<= 1.29>= 6.3, <= 6.3.11>= 6.5.0, <= 6.5.3>= 7.0, <= 7.2.1CVSS 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 Movable Type versionLocate the installed Movable Type version number. This is typically displayed in the Movable Type admin dashboard (usually on the dashboard or system overview page) or can be found in Movable Type's version configuration file or mt-config.cgi file.Affected if The installed version matches one of these ranges: <= 1.29; >= 6.3 and <= 6.3.11; >= 6.5.0 and <= 6.5.3; >= 7.0 and <= 7.2.1.
-
Confirm Movable Type editionVerify that the installation is Sixapart Movable Type (not Movable Type Open Source or other variants). The vulnerability applies specifically to Sixapart Movable Type versions within the affected ranges.Affected if The installed product is Sixapart Movable Type and the version falls within the affected ranges.
-
Check for user input handlingReview anyMovable Type templates, plugins, or custom fields that accept and display user-supplied data. The XSS vulnerability exists in howMovable Type handles unsanitized input in various components.Affected if TheMovable Type installation processes and displays user-generated content through templates, comments, or custom fields, and the version is within the affected ranges.
A user is affected if theirMovable Type installation is the Sixapart commercial edition and the installed version falls within any of these ranges: <= 1.29, 6.3 through 6.3.11, 6.5.0 through 6.5.3, or 7.0 through 7.2.1.
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 the latest patched version of Movable Type (Movable Type 7.2.2+, Movable Type 6.5.4+, Movable Type 6.3.12+, Movable Type Premium 1.30+). If immediate patching is not feasible, implement output encoding and input validation on all user-supplied data fields as a temporary workaround.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5575 — 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-5575 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