CVE Intelligence
Skip to main content
MEDIUM

CVE-2025-24841

CVE-2025-24841 Vulnerability Analysis & Exploit Intelligence

Movable Type contains a stored cross-site scripting vulnerability in the HTML edit mode of MT Block Editor. It is exploitable when TinyMCE6 is used as a rich text editor and an arbitrary script may be executed on a logged-in user's web browser.

Published Updated Sources: cvelistV5, jpcert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

six apart

8 products listed

CVSS base

5.4

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (8)

movable type 8 4 x seriesmovable type 8 0 x seriesmovable type advanced 8 4 x seriesmovable type advanced 8 0 x seriesmovable type premium 2 x seriesmovable type premium advanced edition 2 x seriesmovable type cloud edition 8 x seriesmovable type premium cloud edition 2 x series

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.4CVSS 3.0MEDIUMcvelistV5

Weakness & attack patterns

  • CWE-79

References

2 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.