Security readout for executives and security teams
Plain-English summary
This issue lets a remote attacker use crafted wiki content to expose the IP addresses of people viewing affected MediaWiki pages. The direct impact is privacy loss for visitors rather than server takeover. The source data names fixed MediaWiki releases, but provides no CVSS score or confirmed active exploitation.
Executive priority
Treat this as a privacy and trust issue, not a critical infrastructure compromise. Prioritize upgrades for public wikis and communities where visitor IP disclosure creates safety, compliance, or reputational risk.
Technical view
MediaWiki versions before 1.23.16, 1.24.x through 1.27.x before 1.27.2, and 1.28.x before 1.28.1 allowed IP disclosure through attacker-controlled URL handling in a style/title attribute interaction. The record does not provide CWE, CVSS, CPEs, or detailed exploit maturity evidence.
Likely exposure
Exposure is likely limited to internet-facing or externally accessible MediaWiki installations running the listed vulnerable versions, especially where untrusted users can create or edit page content.
Exploitation context
The CVE record describes remote attacker capability to discover visitor IP addresses. It is not listed as KEV, and the supplied sources do not show confirmed active exploitation.
Researcher notes
Evidence is sparse: the CVE names affected release ranges and the disclosure mechanism, but lacks CVSS, CWE, CPE, and exploitation confirmation. Avoid assuming broader MediaWiki branches or products beyond the listed versions.
Mitigation direction
- Upgrade affected MediaWiki instances to 1.23.16, 1.27.2, 1.28.1, or later supported releases.
- Review Wikimedia/MediaWiki guidance in the referenced Phabricator issues.
- Restrict untrusted content editing until vulnerable instances are upgraded.
- Assess privacy impact for communities requiring visitor anonymity.
Validation and detection
- Inventory all MediaWiki deployments and record exact versions.
- Confirm no instance runs the vulnerable version ranges listed in the CVE.
- Review page-edit permissions for untrusted or anonymous contributors.
- Check web logs for unusual third-party resource requests tied to wiki page views.
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.
CVE-2017-0371 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://phabricator.wikimedia.org/T140591CVE reference · x_refsource_MISC
- https://phabricator.wikimedia.org/T68404CVE reference · x_refsource_MISC
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.