CVE-2018-0672
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 versions prior to Ver. 6.3.1 allows remote attackers to inject arbitrary web 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 · moderate confidenceCross-site scripting (XSS) vulnerability in Movable Type CMS versions prior to 6.3.1 allows remote attackers to inject arbitrary web script or HTML. The specific attack vector is not detailed in available documentation, but the flaw is exploitable remotely without authentication based on the CVSS attack vector.
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< 6.3.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.0/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.
-
Locate Movable Type installation directoryIdentify the web server document root or directory where Movable Type files are hosted. Look for the 'mt' directory containing core Movable Type files such as mt-config.cgi, mt.cgi, and other MT scripts.Affected if The Movable Type installation exists in the environment.
-
Find the Movable Type version fileIn the Movable Type installation directory, look for a VERSION file, RELEASE file, or similar version identifier. This file typically contains the exact version number of the installed Movable Type instance.Affected if A VERSION or RELEASE file exists in the Movable Type installation directory.
-
Check version in Movable Type admin interfaceLog into the Movable Type admin dashboard (usually at /mt.cgi or /mt/mt.cgi) and navigate to the system overview or 'About' section which displays the installed Movable Type version number.Affected if Access to Movable Type admin interface is available and shows the version.
-
Compare installed version to affected rangeTake the version number identified from the VERSION file or admin interface and compare it numerically to 6.3.1. Versions less than 6.3.1 (such as 6.3.0, 6.2.x, 6.1.x, etc.) are affected by this vulnerability.Affected if The installed version is less than 6.3.1.
A user is affected if Movable Type CMS is installed and the detected version is lower than 6.3.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 data6.3.1
Upgrade Movable Type to version 6.3.1 or later to receive the security patch. Alternatively, apply any vendor-supplied patches for this vulnerability.
- 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-2018-0672 — 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-2018-0672 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