# CVE-2025-32697: Cascading protection is not preventing file reversions

> Attackers can bypass cascading protection to revert files, allowing unauthorized modification of protected content in MediaWiki installations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Apr 2025
- **Updated:** 10 Apr 2025
- **Also known as:** BIT-mediawiki-2025-32697, DEBIAN-CVE-2025-32697, GHSA-f626-w254-w424, UBUNTU-CVE-2025-32697

## What is CVE-2025-32697?

CVE-2025-32697 is a missing authorization vulnerability in Wikimedia Foundation MediaWiki, published on 10 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper Preservation of Permissions vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/editpage/IntroMessageBuilder.Php, includes/Permissions/PermissionManager.Php, includes/Permissions/RestrictionStore.Php.

This issue affects MediaWiki: before 1.42.6, 1.43.1.

Weakness: CWE-281 (Improper Preservation of Permissions)

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

1 open source package ship an affected version, including mediawiki.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mediawiki` | Bitnami | All versions | 1.43.1 |

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

Upgrade mediawiki to 1.43.1 or later.

## Is CVE-2025-32697 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32697 is a missing authorization vulnerability in Wikimedia Foundation MediaWiki, published on 10 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-32697 in the wild and no public exploit code.

Affected packages and fixed versions:
- mediawiki (Bitnami): affected all versions; fixed in 1.43.1

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-32697/ (Markdown: https://insights.sbomify.com/CVE-2025-32697/index.md)
```

## Sources

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

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