# CVE-2025-53522: Other in Movable Type (Cloud Edition)

> Remote unauthenticated attackers can send tampered password reset emails to compromise user accounts in Movable Type.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 20 Aug 2025
- **Also known as:** GHSA-q3q7-94pw-4c94

## What is CVE-2025-53522?

CVE-2025-53522 is a medium-severity vulnerability in Six Apart Ltd. Movable Type (Cloud Edition), published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Movable Type contains an issue with use of less trusted source. If exploited, tampered email to reset a password may be sent by a remote unauthenticated attacker.

Weakness: CWE-348 (Use of Less Trusted Source)

## Which versions are affected by CVE-2025-53522?


## How do I fix CVE-2025-53522?

No fix has been published for CVE-2025-53522 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53522 being exploited?

There is no known exploitation of CVE-2025-53522 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53522 and fix it if it is affected.

What it is: CVE-2025-53522 is a medium-severity vulnerability in Six Apart Ltd. Movable Type (Cloud Edition), published on 20 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53522 in the wild and no public exploit code.

Affected product: Six Apart Ltd. Movable Type (Cloud Edition). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53522/ (Markdown: https://insights.sbomify.com/CVE-2025-53522/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53522
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53522
- OSV: https://osv.dev/vulnerability/CVE-2025-53522

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53522/
Summaries are generated and may contain mistakes; the official description above is the record.