CVE-2025-32956

Miraheze Managewiki SQL injection

8.0 HIGHPublic exploitEPSS 0.67%

Published21 Apr 2025

Description

ManageWiki is a MediaWiki extension allowing users to manage wikis. Versions before commit f504ed8, are vulnerable to SQL injection when renaming a namespace in Special:ManageWiki/namespaces when using a page prefix (namespace name, which is the current namespace you are renaming) with an injection payload. This issue has been patched in commit f504ed8. A workaround for this vulnerability involves setting `$wgManageWiki['namespaces'] = false;`.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionRequired

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected products

Miraheze Managewiki< 2025-04-20

Remediation

Fixed in

Miraheze Managewiki≥ 2025-04-20

Patch & vendor advisories

References

https://github.com/miraheze/ManageWiki/commit/f504ed8eeb59b57ebb90f93cd44f23da4c5bc4c9Patch
https://github.com/miraheze/ManageWiki/security/advisories/GHSA-gg42-cv66-f5x7MitigationVendor Advisory
https://www.vicarius.io/vsociety/posts/cve-2025-32956-detect-mediawiki-vulnerabilityExploitThird Party Advisory
https://www.vicarius.io/vsociety/posts/cve-2025-32956-mitigate-mediawiki-vulnerabilityExploitMitigationThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-32956 being actively exploited?

CVE-2025-32956 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.67%.

How severe is CVE-2025-32956?

CVE-2025-32956 has a CVSS 3.1 base score of 8.0, rated high. EPSS estimates a 0.67% probability of exploitation.

Which products are affected by CVE-2025-32956?

Affected products include Miraheze Managewiki.

How do I fix CVE-2025-32956?

Upgrade affected software to a fixed version, for example Miraheze Managewiki 2025-04-20 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-32956 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.