dbcve.org
MediawikiCMS

CVE-2025-61643

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.39.14 / 1.43.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/recentchanges/RecentChangeRCFeedNotifier.Php. This issue affects MediaWiki: from * before 1.39.14, 1.43.4, 1.44.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Vulnerability in MediaWiki's RecentChangeRCFeedNotifier.php file, which handles the Recent Changes feed notification system. The specific nature (XSS, injection, etc.) is not detailed in the available description, but it affects the notification pipeline for recent changes.

MitigationUpdate MediaWiki to version 1.39.14, 1.43.4, or 1.44.1 (or later) to receive the security patch for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MediawikiCMS
Affected:< 1.39.14>= 1.43.0, < 1.43.4= 1.44.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MediaWiki version
    Locate the file 'includes/Defines.php' or run 'php maintenance/run.php version' from the MediaWiki installation directory. Look for the $wgVersion variable.
    Affected if The installed version is < 1.39.14, OR >= 1.43.0 and < 1.43.4, OR exactly 1.44.0
  2. Verify RCFeed notification system is configured
    Check your LocalSettings.php file for any $wgRCFeeds configuration entries. Also check any feed-specific configuration such as $wgRCStream or custom feed handlers.
    Affected if The RecentChangeRCFeedNotifier.php is actively used when $wgRCFeeds is configured with any enabled feed handlers.
  3. Confirm RecentChangeRCFeedNotifier.php is present
    Locate the file 'includes/rcfeed/RecentChangeRCFeedNotifier.php' within your MediaWiki installation directory and verify it exists.
    Affected if The file is present in versions that are affected (any installation matching the version ranges above).

You are affected if your MediaWiki version falls within < 1.39.14, >= 1.43.0 and < 1.43.4, or = 1.44.0 AND the Recent Changes feed notification system is enabled via $wgRCFeeds configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.39.14 / 1.43.4 or later
Fixed in 1.39.141.43.4
Interim mitigation

Update MediaWiki to version 1.39.14, 1.43.4, or 1.44.1 (or later) to receive the security patch for this vulnerability.

Recommended fix High confidence

Upgrade to MediaWiki 1.39.14 (LTS), 1.43.4, or 1.44.1 depending on your branch

  1. 1. Identify your current MediaWiki version by checking the file `includes/Defines.php` or the version history in your admin interface.
  2. 2. Determine which upgrade path applies to your installation: if you are on the 1.39.x LTS branch, upgrade to 1.39.14; if you are on 1.43.x, upgrade to 1.43.4; if you are on 1.44.0, upgrade to 1.44.1.
  3. 3. Back up your MediaWiki database and files before performing the upgrade.
  4. 4. Download the appropriate fixed release from https://www.mediawiki.org/wiki/Download or use your package manager.
  5. 5. Replace the MediaWiki core files with the new version, preserving your `LocalSettings.php` configuration file.
  6. 6. Run the update script `php maintenance/update.php` to apply any necessary database schema changes.
  7. 7. Verify the installation by accessing your wiki and checking the version number in Special:Version.
Caveat Standard MediaWiki upgrades may require checking compatibility of extensions; review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mediawiki Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61643 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data