Security readout for executives and security teams
Plain-English summary
MediaWiki private wiki content could be exposed because REST API responses were publicly cached. The issue affects versions before 1.35.5, 1.36.3, and 1.37.1. Business impact is mainly unintended disclosure of private wiki data, not system takeover or service disruption.
Executive priority
Treat this as a prompt privacy and information-disclosure fix for private MediaWiki deployments. It is not described as a takeover risk, but exposed private wiki content can create business, compliance, and operational risk.
Technical view
CVE-2021-44854 is a CWE-524 caching weakness in MediaWiki. REST API output from private wikis could be cached publicly, allowing unauthenticated access to content that should remain private. CVSS 3.1 is 5.3, with network access, low complexity, no privileges, no user interaction, and low confidentiality impact.
Likely exposure
Organizations running private MediaWiki instances below 1.35.5, 1.36.3, or 1.37.1 are the likely exposure group, especially where REST API responses can pass through public or shared caches.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The weakness is remotely reachable and low complexity, but the documented impact is limited to confidentiality exposure through caching behavior.
Researcher notes
The source bundle identifies the issue and fixed version boundaries but provides limited technical detail. Avoid assuming broader product impact beyond MediaWiki. Focus validation on private wiki REST API caching and whether shared caches retained protected responses.
Mitigation direction
- Upgrade MediaWiki to 1.35.5, 1.36.3, 1.37.1, or later supported releases.
- Apply vendor or distribution security guidance, including Gentoo GLSA-202305-24 where relevant.
- Review shared, proxy, and CDN cache handling for private wiki REST API responses.
- Purge exposed public or shared caches after applying fixes.
- Restrict access to private wiki REST endpoints until fixed, where operationally feasible.
Validation and detection
- Inventory all MediaWiki private wiki deployments and record exact versions.
- Confirm deployed versions are at or above the fixed release lines.
- Review cache configuration for REST API responses from private wikis.
- Check whether shared caches contain private wiki REST responses.
- Verify unauthenticated users cannot receive cached private REST API content.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-524: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-44854 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://phabricator.wikimedia.org/T292763CVE reference
- https://security.gentoo.org/glsa/202305-24CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Cache Containing Sensitive Information
Use of Cache Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.