dbcve.org
Movable TypeApplication · Sixapart

CVE-2019-6025

MEDIUM · 6.1 CVSS v3.1 Published 2019-12-26
Fix available
A fix is available. Upgrade to after 7.1.3 or later.
See remediation →
68/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
Open redirect vulnerability in Movable Type series Movable Type 7 r.4602 (7.1.3) and earlier (Movable Type 7), Movable Type 6.5.0 and 6.5.1 (Movable Type 6.5), Movable Type 6.3.9 and earlier (Movable Type 6.3.x, 6.2.x, 6.1.x, 6.0.x), Movable Type Advanced 7 r.4602 (7.1.3) and earlier (Movable Type 7), Movable Type Advanced 6.5.0 and 6.5.1 (Movable Type 6.5), Movable Type Advanced 6.3.9 and earlier (Movable Type 6.3.x, 6.2.x, 6.1.x, 6.0.x), Movable Type Premium 1.24 and earlier (Movable Type Premium), and Movable Type Premium (Advanced Edition) 1.24 and earlier (Movable Type Premium) allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a specially crafted URL.

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

Open redirect vulnerability in Movable Type allows remote attackers to redirect users to arbitrary external websites via specially crafted URLs. The vulnerability affects multiple versions including Movable Type 7 r.4602 and earlier, 6.5.x, 6.3.x and earlier, and Premium versions up to 1.24, enabling phishing attacks.

MitigationApply vendor patches for CVE-2019-6025 by upgrading to the fixed Movable Type versions, or implement URL validation/allowlist controls at the application or WAF layer to prevent untrusted redirect targets.

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:>= 6.0, <= 6.3.9>= 7.0, <= 7.1.3= 6.5.0= 6.5.1<= 1.24

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
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 checks

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

  1. Locate Movable Type installation
    Search for the mt-config.cgi configuration file in the web root directory, typically found in paths like /cgi-bin/mt/ or /mt/. Also look for the mt.cgi or mt-static directory.
    Affected if Movable Type is not found in the environment, meaning this CVE does not apply.
  2. Identify installed Movable Type version
    Open mt-config.cgi and look for the 'Database' or 'ObjectDriver' configuration lines, or check theMovable Type admin dashboard (usually at /mt/cgi-bin/mt.cgi or /mt/index.html) for the version displayed on the login or about page.
    Affected if Unable to determine the version, preventing comparison to affected ranges.
  3. Compare version against affected ranges
    Match your installed version to these vulnerable ranges: 6.0 through 6.3.9, 6.5.0 through 6.5.1, 7.0 through 7.1.3, or Premium versions 1.24 and below.
    Affected if The installed version falls within any of these ranges: 6.0-6.3.9, 6.5.0-6.5.1, 7.0-7.1.3, or Premium ≤1.24.
  4. Verify vulnerable endpoint accessibility
    Test if the Movable Type CGI scripts are accessible by attempting to access common entry points such as /mt/cgi-bin/mt.cgi, /mt/mt.cgi, or /mt/ (the web root). The open redirect vulnerability can be triggered through specially crafted URLs with a redirect parameter.
    Affected if The Movable Type CGI scripts are publicly accessible without additional authentication controls.

If your Movable Type version is 6.0-6.3.9, 6.5.0-6.5.1, 7.0-7.1.3, or Premium ≤1.24 and the CGI scripts are accessible, your environment is affected by this open redirect vulnerability.

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.

From vendor data
Upgrade available Upgrade to a release after 7.1.3
Interim mitigation

Apply vendor patches for CVE-2019-6025 by upgrading to the fixed Movable Type versions, or implement URL validation/allowlist controls at the application or WAF layer to prevent untrusted redirect targets.

Fix this in Movable Type Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6025 — 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-2019-6025 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