CVE-2022-45122
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 Movable Type 7 r.5301 and earlier (Movable Type 7 Series), Movable Type Advanced 7 r.5301 and earlier (Movable Type Advanced 7 Series), Movable Type 6.8.7 and earlier (Movable Type 6 Series), Movable Type Advanced 6.8.7 and earlier (Movable Type Advanced 6 Series), Movable Type Premium 1.53 and earlier, and Movable Type Premium Advanced 1.53 and earlier allows a remote unauthenticated attacker to inject an arbitrary script.
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 allows remote unauthenticated attackers to inject arbitrary JavaScript or HTML into web pages served by the application. The vulnerability affects multiple product lines (Movable Type 7, Movable Type Advanced 7, Movable Type 6, Movable Type Advanced 6, Movable Type Premium, and Movable Type Premium Advanced) at specified version thresholds.
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.53>= 6.0, < 6.8.7>= 7.0, < 7.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.
-
Locate the Movable Type version numberCheck the Movable Type admin dashboard (typically at /mt/admin/ or /cgi-bin/mt/admin.cgi) by logging in and viewing the system overview or settings page. Alternatively, check for a version file in the installation directory, commonly named 'VERSION' or 'mt-version.cgi' in the Movable Type root folder.Affected if The displayed version matches <= 1.53, OR >= 6.0 and < 6.8.7, OR >= 7.0 and < 7.9.6
-
Confirm the Movable Type product variantIdentify whether the installation is Movable Type (standard), Movable Type Advanced, Movable Type Premium, or Movable Type Premium Advanced. This is typically visible in the admin dashboard header or system information page.Affected if Any of the listed product variants (standard, Advanced, Premium, Premium Advanced) are running an affected version from step 1
-
Identify publicly accessible input formsReview the Movable Type site for publicly accessible features that accept user input, such as comment submission forms, search boxes, guestbook entries, or community submission pages. These are common vectors for XSS exploitation.Affected if Publicly accessible user input forms are present and functional on the Movable Type site
-
Check if output encoding is applied to user inputsInspect the HTML source code of pages with user input forms (view source in browser). Look for proper HTML encoding of user-supplied values, such as conversion of <script> to <script> or similar escaping of special characters.Affected if User input fields do not appear to have output encoding applied, meaning special characters are rendered as-is without escaping
The environment is affected if Movable Type (any variant) is installed at version 1.53 or below, or at version 6.0 through 6.8.7, or at version 7.0 through 7.9.6, and the system has publicly accessible input fields without proper output encoding.
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.
dbcve · scoped6.8.77.9.6
Upgrade to Movable Type versions r.5302 or later for version 7 series, 6.8.8 or later for version 6 series, or 1.54 or later for Premium versions. Alternatively, apply vendor-provided patches and implement output encoding on user-supplied input fields.
Movable Type 6.8.7, Movable Type 7.9.6, or Movable Type Premium 1.54+ (depending on product line)
- 1. Identify the Movable Type product variant and current version running in your environment (MT, MT Advanced, MT Premium, or MT Premium Advanced)
- 2. For Movable Type 6.x series (6.0 to 6.8.6): Upgrade to version 6.8.7
- 3. For Movable Type 7.x series (7.0 to 7.9.5): Upgrade to version 7.9.6
- 4. For Movable Type Premium 1.53 and earlier: Upgrade to version 1.54 or later
- 5. For Movable Type Premium Advanced 1.53 and earlier: Upgrade to version 1.54 or later
- 6. After upgrade, verify the Movable Type installation is functioning correctly
- 7. Test that the XSS vulnerability is no longer present by reviewing release notes for security fixes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45122 — 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-2022-45122 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