Wikimedia CentralAuth Extension up to 1.43.6/1.44.3/1.45.1 on Mediawiki improper removal of sensitive information before storage or transfer
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Wikimedia CentralAuth Extension up to 1.43.6/1.44.3/1.45.1 on Mediawiki. The impacted element is an unknown function. Performing a manipulation results in improper removal of sensitive information before storage or transfer. This vulnerability is cataloged as CVE-2026-39937. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Wikimedia CentralAuth Extension up to 1.43.6/1.44.3/1.45.1 on Mediawiki. This affects an unknown code. The manipulation with an unknown input leads to a improper removal of sensitive information before storage or transfer vulnerability. CWE is classifying the issue as CWE-212. The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Improper removal of sensitive information before storage or transfer vulnerability in The Wikimedia Foundation Mediawiki - CentralAuth Extension allows Resource Leak Exposure.This issue affects non release branches.
The weakness was shared by Urbanecm. The advisory is shared at phabricator.wikimedia.org. This vulnerability is uniquely identified as CVE-2026-39937 since 04/07/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 1.43.7, 1.44.4 or 1.45.2 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper removal of sensitive information before storage or transferCWE: CWE-212 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: CentralAuth Extension 1.43.7/1.44.4/1.45.2
Timeline
04/07/2026 CVE reserved04/08/2026 Advisory disclosed
04/08/2026 VulDB entry created
04/08/2026 VulDB entry last update
Sources
Advisory: phabricator.wikimedia.orgResearcher: Urbanecm
Status: Confirmed
CVE: CVE-2026-39937 (🔒)
GCVE (CVE): GCVE-0-2026-39937
GCVE (VulDB): GCVE-100-355989
Entry
Created: 04/08/2026 07:47Changes: 04/08/2026 07:47 (68)
Complete: 🔍
Cache ID: 216:B61:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.