dbcve.org
Movable TypeApplication · Sixapart

CVE-2026-25776

CRITICAL · 9.8 CVSS v3.0 Published 2026-04-08
Fix available
A fix is available. Upgrade to 8.0.10 / 8.8.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Movable Type provided by Six Apart Ltd. contains a code injection vulnerability which may allow an attacker to execute arbitrary Perl 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 · moderate confidence

Movable Type CMS contains a code injection vulnerability that allows an unauthenticated attacker to execute arbitrary Perl code on the server. This remote code execution (RCE) flaw is remotely exploitable over the network and can lead to complete system compromise.

MitigationApply the vendor-supplied patch or upgrade to a fixed version of Movable Type immediately. Isolate the affected system from untrusted networks and conduct a post-deployment compromise assessment.

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:<= 2.14= 9.0.5= 9.0.6= 9.1.0>= 8.0.2, < 8.0.10>= 8.8.0, < 8.8.3>= 9.0.1, < 9.0.7

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm Movable Type is present
    Search for Movable Type installation directories or examine web server configurations for Movable Type signatures
    Affected if Movable Type web publishing platform is installed on the system
  2. Identify Movable Type version
    Retrieve version information from Movable Type admin interface, configuration files, or version detection mechanisms within the installation
    Affected if Installed version is <=2.14, =9.0.5, =9.0.6, =9.1.0, >=8.0.2 and <8.0.10, >=8.8.0 and <8.8.3, or >=9.0.1 and <9.0.7
  3. Verify vulnerable component is accessible
    Check Movable Type configuration settings and module status to determine if the code injection vector is enabled and reachable
    Affected if The vulnerable component or feature that allows arbitrary Perl script execution is accessible to authenticated or unauthenticated users

Environment is affected if Movable Type is installed with a version matching any of the specified vulnerable ranges and the exploitable functionality is enabled

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 8.0.10 / 8.8.3 / 9.0.7 or later
Fixed in 8.0.108.8.39.0.7
Interim mitigation

Apply the vendor-supplied patch or upgrade to a fixed version of Movable Type immediately. Isolate the affected system from untrusted networks and conduct a post-deployment compromise assessment.

Recommended fix Moderate confidence

Movable Type 9.1.1 or latest stable release (upgrade from affected versions 9.0.5, 9.0.6, 9.1.0)

  1. Identify the currently installed Movable Type version by checking the mt-config.cgi file or the Movable Type admin dashboard
  2. Review the official Movable Type security advisories at movabletype.org and Six Apart Japan's security notifications at www.sixapart.jp for the specific fixed version corresponding to CVE-2026-25776
  3. Download the latest stable Movable Type release (version 9.1.1 or later, as versions 9.0.5, 9.0.6, and 9.1.0 are affected) from the official movabletype.org download page
  4. Before applying the upgrade, perform a complete backup of the Movable Type installation directory and the associated database
  5. Place the application in maintenance mode or take it offline to prevent active attacks during the upgrade process
  6. Extract and upload the new Movable Type files, overwriting the existing installation while preserving mt-config.cgi and any custom theme/plugin directories
  7. Run the upgrade scripts as documented in the Movable Type upgrade guide
  8. Verify the upgrade was successful by logging into the Movable Type admin panel and checking the system information
Caveat Upgrade may require PHP/Perl module compatibility checks; custom plugins may need verification for 9.x compatibility; review migration notes for any configuration changes

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

Fix this in Movable Type Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
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,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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