dbcve.org
Movable TypeApplication · Sixapart

CVE-2022-45113

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-07
Fix available
A fix is available. Upgrade to 6.8.7 / 7.9.6 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper validation of syntactic correctness of input vulnerability exist in Movable Type series. Having a user to access a specially crafted URL may allow a remote unauthenticated attacker to set a specially crafted URL to the Reset Password page and conduct a phishing attack. Affected products/versions are as follows: 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.

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 confidence

Improper input validation in Movable Type's password reset functionality allows remote unauthenticated attackers to manipulate the URL parameter sent to the Reset Password page. This enables attackers to set a malicious URL as the redirect target after password reset, facilitating phishing attacks against users who request a password reset.

MitigationApply vendor-supplied patches for Movable Type series to version r.5302 or later for version 7, 6.8.8 for version 6, and 1.54 for Premium versions. As an interim measure, monitor password reset traffic for suspicious URL parameters and warn users to verify the URL before entering credentials.

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
Movable TypeApplication
Affected:<= 1.53>= 6.0, < 6.8.7>= 7.0, < 7.9.6

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Movable Type installation version
    Check the version file in your Movable Type installation directory, or log into the admin dashboard and look for the version number typically displayed in the footer or system information page
    Affected if The installed version falls within <=1.53, >=6.0 and <6.8.7, or >=7.0 and <7.9.6
  2. Confirm password reset functionality is enabled
    Access the Movable Type login page and verify that a password reset or forgot password option is present and functional
    Affected if Password reset functionality is accessible to unauthenticated users (this is the default configuration)
  3. Identify the password reset redirect mechanism
    Examine the password reset form or the URL generated when requesting a password reset - look for any redirect or return_to URL parameter in the request
    Affected if The password reset flow accepts a user-controllable redirect URL parameter without validation (requires code review or testing to confirm)
  4. Compare against fixed versions
    Document your current version and compare against the fixed releases: 6.8.8, 7.9.6, or 1.54 for Premium
    Affected if Your version is older than these fixed releases and falls within the affected ranges

You are affected if your Movable Type installation version is <=1.53, between 6.0-6.8.7, or between 7.0-7.9.6, and the password reset feature is enabled (which is the default).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.8.7 / 7.9.6 or later
Fixed in 6.8.77.9.6
Interim mitigation

Apply vendor-supplied patches for Movable Type series to version r.5302 or later for version 7, 6.8.8 for version 6, and 1.54 for Premium versions. As an interim measure, monitor password reset traffic for suspicious URL parameters and warn users to verify the URL before entering credentials.

Recommended fix High confidence

Movable Type 6.8.8+, Movable Type 7.9.7+, or Movable Type Premium 1.54+ (depending on product line)

  1. 1. Identify the Movable Type product and version currently installed (MT 6.x, MT 7.x, MT Premium, or MT Advanced variants)
  2. 2. For Movable Type 6.x installations: upgrade to version 6.8.8 or later
  3. 3. For Movable Type 7.x installations: upgrade to version 7.9.7 or later
  4. 4. For Movable Type Premium 1.53 and earlier: upgrade to version 1.54 or later
  5. 5. After upgrade, verify the installation is functioning correctly
  6. 6. Test the password reset functionality to confirm the vulnerability is remediated
Caveat Standard upgrade precautions apply - backup database and files before upgrading, test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Movable Type Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45113 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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