dbcve.org
Movable TypeApplication · Sixapart

CVE-2026-33088

CRITICAL · 9.8 CVSS v3.1 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 an SQL Injection vulnerability which may allow an attacker to execute an arbitrary SQL statement.

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, a content management system from Six Apart Ltd., contains an SQL injection vulnerability with a critical CVSS score of 9.8. The flaw allows authenticated or unauthenticated attackers (exact requirements unspecified) to inject and execute arbitrary SQL statements via unsanitized input parameters in the application.

MitigationApply vendor patches or updates as soon as available; in the interim, implement strict input validation, use parameterized queries/prepared statements, and restrict database permissions to limit impact of potential exploitation.

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:>= 8.0.2, < 8.0.10>= 8.8.0, < 8.8.3>= 9.0.1, < 9.0.7= 9.1.0<= 2.14= 9.0.5= 9.0.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 installed
    Locate the Movable Type installation directory or check for 'mt-config.cgi' file typically found in the Movable Type root folder. On Linux systems, common paths include /var/www/html/mt, /opt/mt, or within the web server's document root.
    Affected if Movable Type software is not present on the system
  2. Determine installed Movable Type version
    Check the version file in the Movable Type installation. The version is often listed in a VERSION file, in the mt-config.cgi configuration file, or displayed on the Movable Type login page. Look for a file named 'VERSION' or 'mt-version' in the installation directory.
    Affected if The installed version cannot be determined or the installation is a version not listed in the affected ranges
  3. Compare installed version against affected ranges
    Compare your installed version number to the affected ranges: 8.0.2 through 8.0.9; 8.8.0 through 8.8.2; 9.0.1 through 9.0.6; 9.1.0; and any version <= 2.14. If your version matches any of these, the installation is vulnerable.
    Affected if The installed version falls within or matches any of the affected version ranges listed
  4. Verify admin interface network exposure
    Determine if the Movable Type admin interface (typically at /mt/ or /cgi-bin/mt/) is accessible from untrusted networks. Use a browser or curl to attempt access to the admin login page from an external IP address, or review firewall rules and web server access controls.
    Affected if The Movable Type admin interface is accessible from untrusted network segments without authentication

A system is affected if it runs any version of Sixapart Movable Type matching the listed affected versions AND the admin interface is network-accessible, allowing unauthenticated remote attackers to inject arbitrary SQL statements.

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 vendor patches or updates as soon as available; in the interim, implement strict input validation, use parameterized queries/prepared statements, and restrict database permissions to limit impact of potential exploitation.

Recommended fix High confidence

Upgrade to 8.0.10 (for 8.0.x), 8.8.3 (for 8.8.x), 9.0.7 (for 9.0.x), or 9.1.1 or later (for 9.1.0)

  1. 1. Log into your Movable Type admin dashboard and verify the current version under "System Settings" or "About".
  2. 2. Create a complete backup of your Movable Type installation including the database and all files.
  3. 3. Review the official Movable Type upgrade documentation at movabletype.org for your current version.
  4. 4. Download the appropriate fixed version for your release line from the official Movable Type download page.
  5. 5. Upload and install the fixed Movable Type version following the standard upgrade procedure.
  6. 6. Clear all caches and rebuild the site after upgrade to ensure all templates are properly compiled.
  7. 7. Verify the upgrade was successful by checking the version number and testing core functionality.
Caveat Standard Movable Type upgrade risks apply - always test on staging first, review plugin compatibility, and backup before upgrading

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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