☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2025-32964

CVE-2025-32964 Supply Chain Attack in Mediawiki
📅 PUBLISHED: 2025-04-22 17:15 UTC 🔄 UPDATED: 2026-09-23 20:34 UTC
[ OFFICIAL PATCH DEPLOYED ↓ ] FIX: LIKELY — 2 independent sources confirm fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.22%
👁️
0.22% probability
5.4× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
Patch available — upgrade to latest release
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
4.6
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-32964 is a missing authorization vulnerability in the ManageWiki extension for MediaWiki. The flaw allows a user with basic permissions to inadvertently disable a restricted extension by enabling a conflicting extension. This bypasses the intended authorization check that should require the ManageWiki-restricted right. The vulnerability has a CVSS score of 4.6 (Medium) and is patched in commit 00bebea. No public exploit code or proof-of-concept is currently available.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability affects the ManageWiki extension, which is a third-party MediaWiki extension. The risk is primarily to MediaWiki administrators who rely on this extension to manage wiki configurations. The supply chain risk is moderate, as the extension is not part of the core MediaWiki package but is widely used in wiki farms.

CVSS Breakdown & Threat Level

  • CVSS Score: 4.6 (Medium)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low (user must have basic ManageWiki permissions)
  • User Interaction: None
  • Scope: Unchanged
  • Confidentiality Impact: None
  • Integrity Impact: Low (unauthorized disabling of restricted extensions)
  • Availability Impact: None

Threat Level: Medium. The vulnerability allows a low-privileged user to disable restricted extensions, potentially disrupting wiki functionality or security controls.

Deep Dive & Mechanics

The ManageWiki extension allows users with appropriate permissions to enable and disable extensions on a per-wiki basis. The vulnerability lies in the logic that handles extension conflicts. When a user enables an extension that conflicts with another, the system automatically disables the conflicting extension. However, the authorization check for disabling the conflicting extension was missing. This means a user who does not hold the ManageWiki-restricted right could still disable a restricted extension by enabling a conflicting one.

The core issue is in the conflict resolution code. The system should verify that the user has the ManageWiki-restricted right before disabling a restricted extension. The patched code adds this check.

Vulnerable vs. Patched Code

Vulnerable Code (Conceptual):

// In the conflict resolution function
function resolveConflicts($extensionToEnable) {
    $conflicts = getConflicts($extensionToEnable);
    foreach ($conflicts as $conflict) {
        // Missing authorization check
        disableExtension($conflict);
    }
    enableExtension($extensionToEnable);
}

Patched Code (Conceptual):

function resolveConflicts($extensionToEnable) {
    $conflicts = getConflicts($extensionToEnable);
    foreach ($conflicts as $conflict) {
        // Added authorization check
        if (isRestricted($conflict) && !userHasRight('ManageWiki-restricted')) {
            throw new PermissionException('You do not have permission to disable this restricted extension.');
        }
        disableExtension($conflict);
    }
    enableExtension($extensionToEnable);
}

Exploitation & Lab Setup

Red Team

Prerequisites:

  • Access to a MediaWiki instance with ManageWiki extension installed (pre-commit 00bebea).
  • A user account with basic ManageWiki permissions (e.g., managewiki right) but NOT the ManageWiki-restricted right.

Exploitation Steps:

  1. Identify a restricted extension (e.g., RestrictedExtension) that conflicts with a non-restricted extension (e.g., NormalExtension).
  2. As the low-privileged user, navigate to the ManageWiki interface.
  3. Attempt to enable NormalExtension.
  4. The system will automatically disable RestrictedExtension due to the conflict, bypassing the authorization check.

Expected Outcome: The restricted extension is disabled, even though the user lacks the required permission.

Blue Team

Detection:

  • Monitor ManageWiki logs for unexpected disabling of restricted extensions.
  • Alert on any user without the ManageWiki-restricted right performing actions that disable restricted extensions.

Hunting:

  • Search for log entries where a restricted extension was disabled by a user who does not have the ManageWiki-restricted right.
  • Review recent changes to extension configurations in the wiki.

Mitigation:

  • Apply the patch (commit 00bebea) immediately.
  • As a workaround, ensure that any extensions requiring specific permissions in $wgManageWikiExtensions also require the same permissions for managing any conflicting extensions.

Indicators of Compromise (IOCs)

  • Log Entries: Unexpected disabling of restricted extensions in ManageWiki logs.
  • User Actions: Users with only basic ManageWiki permissions disabling restricted extensions.
  • Configuration Changes: Sudden changes to the enabled extensions list, particularly disabling of restricted extensions.

Detection Engineering

YARA Rule

rule CVE_2025_32964_ManageWiki_AuthBypass {
    meta:
        description = "Detects vulnerable ManageWiki extension code"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-32964"
    strings:
        $vuln_func = "resolveConflicts" nocase
        $missing_check = "disableExtension" nocase
    condition:
        $vuln_func and $missing_check and not for any of ($patch_check*)
}

Sigma Rule

title: ManageWiki Restricted Extension Disabled by Unauthorized User
id: 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d
status: experimental
description: Detects when a restricted extension is disabled by a user without the ManageWiki-restricted right
logsource:
    product: mediawiki
    service: managewiki
detection:
    selection:
        EventID: 'managewiki-extension-disabled'
        ExtensionType: 'restricted'
        UserRight: '!ManageWiki-restricted'
    condition: selection
falsepositives:
    - Legitimate administrative actions if logging is misconfigured
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2025-32964 ManageWiki Restricted Extension Disable Attempt"; flow:to_server; content:"POST"; http_method; content:"/wiki/Special:ManageWiki"; http_uri; content:"extension="; http_uri; content:"action=enable"; http_uri; pcre:"/extension=[^&]+&action=enable/"; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate:

  • Apply the patch from commit 00bebea to the ManageWiki extension.
  • Verify that the patch is applied correctly by testing the conflict resolution with a restricted extension.

Workaround:

  • Ensure that any extensions requiring specific permissions in $wgManageWikiExtensions also require the same permissions for managing any conflicting extensions.

Long-term:

  • Review all authorization checks in the ManageWiki extension to ensure they are consistent.
  • Implement regular security audits of MediaWiki extensions.
  • Monitor for any similar authorization bypass vulnerabilities.

Valters IT Signature: This report was generated by Valters IT DevSecOps AI. For questions, contact security@valters.it.

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-32964/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.