dbcve.org
Movable TypeApplication · Sixapart

CVE-2022-43660

HIGH · 7.2 CVSS v3.1 Published 2022-12-07
Fix available
A fix is available. Upgrade to 7.9.6 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Improper neutralization of Server-Side Includes (SSW) within a web page in Movable Type series allows a remote authenticated attacker with Privilege of 'Manage of Content Types' may execute an arbitrary Perl script and/or an arbitrary OS command. 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 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

This is a Server-Side Include (SSI) injection vulnerability in Movable Type. An authenticated attacker with 'Manage of Content Types' privilege can inject malicious SSI directives to execute arbitrary Perl code and OS commands on the server.

MitigationUpgrade to Movable Type versions r.5302 or later (for MT 7) and Premium 1.54 or later. If immediate patching is not possible, consider restricting the 'Manage of Content Types' privilege to only trusted users and disabling SSI processing at the web server level.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify Movable Type version
    Locate the Movable Type version number from the admin interface (typically shown on the dashboard or system overview) or from version files in the MT installation directory
    Affected if The installed version is 7.0 through 7.9.5, or version 1.53 or earlier (all versions before 7.9.6 and r.5302)
  2. Confirm Manage of Content Types privilege exists
    Access the Movable Type admin panel and navigate to System > Users or System > Roles to verify whether any user accounts or roles have the 'Manage of Content Types' permission enabled
    Affected if The privilege is present and assigned to any user account (even without active use, the vulnerability exists in the code)
  3. Check if Content Type functionality is in use
    In the Movable Type admin panel, navigate to Content Types to see if any custom content types have been created and are actively used on the website
    Affected if Content Types are defined and published - this is the attack surface for SSI injection
  4. Review server-side include processing
    Inspect the web server configuration (Apache/nginx) for SSI directives (Include module) and check if .shtml or related file extensions are being processed as Server-Side Includes
    Affected if SSI processing is enabled and .shtml or similar extensions are being parsed by the web server

You are affected if your Movable Type version is 7.0-7.9.5 or <=1.53, and you have users with 'Manage of Content Types' privilege while SSI processing is enabled on your web server.

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 7.9.6 or later
Fixed in 7.9.6
Interim mitigation

Upgrade to Movable Type versions r.5302 or later (for MT 7) and Premium 1.54 or later. If immediate patching is not possible, consider restricting the 'Manage of Content Types' privilege to only trusted users and disabling SSI processing at the web server level.

Recommended fix Moderate confidence

Movable Type 7.9.6 or later; Movable Type Premium > 1.53

  1. 1. Back up your Movable Type installation and database before proceeding with any upgrade.
  2. 2. Identify your current Movable Type version (Movable Type 7, Movable Type Advanced 7, Movable Type Premium, or Movable Type Premium Advanced).
  3. 3. For Movable Type 7 Series (including Movable Type Advanced 7): upgrade to version 7.9.6 or later.
  4. 4. For Movable Type Premium (and Premium Advanced): upgrade to a version newer than 1.53.
  5. 5. After upgrading, verify that the Manage of Content Types functionality works correctly.
  6. 6. Test that the code injection vulnerability is no longer present by confirming arbitrary Perl/OS command execution is not possible through Content Type management.
Caveat Review Movable Type release notes for 7.9.6 for any compatibility changes or deprecated features 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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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