Secuno
ENNL
Book demo

CVE-2025-67484

Mediawiki vulnerability

9.8 CRITICALEPSS 0.45%
  1. Published3 Feb 2026

Description

Vulnerability in Wikimedia Foundation MediaWiki. This vulnerability is associated with program files includes/Api/ApiFormatXml.Php. This issue affects MediaWiki: from * before 1.39.16, 1.43.6, 1.44.3, 1.45.1.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Mediawiki≥ 1.39.0 < 1.39.16 · ≥ 1.43.0 < 1.43.6 · ≥ 1.44.0 < 1.44.3 · 1.45.0

Remediation

Fixed in
Mediawiki≥ 1.39.16

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-843178.8
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1,…
CVE-2026-843168.8
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1,…
CVE-2026-571438.8
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.62,…
CVE-2026-1034138.8
Improper input validation vulnerability in Apache Camel Karavan. When a deployment…
CVE-2026-764688.2
As part of Cisco's ongoing commitment to proactive security and product quality, the…
CVE-2026-764568.6
As part of Cisco's ongoing commitment to proactive security and product quality, the…

Frequently asked

Is CVE-2025-67484 being actively exploited?

CVE-2025-67484 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.45%.

How severe is CVE-2025-67484?

CVE-2025-67484 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.45% probability of exploitation.

Which products are affected by CVE-2025-67484?

Affected products include Mediawiki.

How do I fix CVE-2025-67484?

Upgrade affected software to a fixed version, for example Mediawiki 1.39.16 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-67484 against the real software inventory on every managed device, as each hourly inventory arrives. 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 worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

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