dbcve.org
MediawikiCMS

CVE-2026-58038

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 1.43.9 / 1.44.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Wikimedia Foundation timeline. This vulnerability is associated with program files includes/Timeline.Php, scripts/EasyTimeline.Pl. This issue affects timeline: from * before 1.46.0, 1.45.4, 1.44.6, 1.43.9.

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 · high confidence

Cross-site scripting (XSS) vulnerability in Wikimedia Foundation's Timeline component allows injection of malicious scripts through unsanitized user input processed by includes/Timeline.php and scripts/EasyTimeline.pl. The vulnerability is present in timeline functionality across multiple affected versions before 1.46.0, 1.45.4, 1.44.6, and 1.43.9.

MitigationUpgrade to version 1.46.0, 1.45.4, 1.44.6, or 1.43.9 (whichever is compatible with the deployment) to obtain the patched Timeline component. Alternatively, implement output encoding and input validation on the Timeline.php and EasyTimeline.pl files to neutralize malicious script payloads.

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.43.0, < 1.43.9>= 1.44.0, < 1.44.6>= 1.45.0, < 1.45.4= 1.46.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. Identify MediaWiki installation
    Locate the MediaWiki installation directory and check for the presence of includes/Timeline.php or scripts/EasyTimeline.pl files. These are the files containing the vulnerable code.
    Affected if The Timeline.php or EasyTimeline.pl files exist in the MediaWiki installation.
  2. Determine MediaWiki version
    Check the file 'includes/Defines.php' or 'includes/Setup.php' for the $wgVersion variable, or look at the version file in the root directory. Alternatively, access the Special:Version page if the web interface is available.
    Affected if The installed version falls within these ranges: >= 1.43.0 and < 1.43.9, OR >= 1.44.0 and < 1.44.6, OR >= 1.45.0 and < 1.45.4, OR equals 1.46.0.
  3. Verify Timeline functionality is in use
    Search the MediaWiki installation for the Timeline extension directory (typically 'extensions/Timeline' or 'extensions/EasyTimeline'). Check LocalSettings.php for lines containing 'wfLoadExtension' or 'require_once' that reference Timeline functionality.
    Affected if The Timeline extension is loaded in LocalSettings.php and timelines are being rendered on the wiki.
  4. Inspect affected files for unsanitized input handling
    Examine includes/Timeline.php and scripts/EasyTimeline.pl for user input variables (such as parameters passed to the timeline) that are not passed through htmlspecialchars or equivalent sanitization functions before output.
    Affected if The code processes user-supplied input for timeline parameters without proper output encoding, allowing script injection.

The environment is affected if MediaWiki is installed with a version in the vulnerable ranges AND the Timeline component is enabled and actively processing user input for timeline generation.

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.43.9 / 1.44.6 / 1.45.4 or later
Fixed in 1.43.91.44.61.45.4
Interim mitigation

Upgrade to version 1.46.0, 1.45.4, 1.44.6, or 1.43.9 (whichever is compatible with the deployment) to obtain the patched Timeline component. Alternatively, implement output encoding and input validation on the Timeline.php and EasyTimeline.pl files to neutralize malicious script payloads.

Recommended fix High confidence

Upgrade to 1.43.9+ (if on 1.43.x), 1.44.6+ (if on 1.44.x), 1.45.4+ (if on 1.45.x), or 1.46.1+ (if on 1.46.0) - prefer latest stable in your branch

  1. Review MediaWiki upgrade documentation at https://www.mediawiki.org/wiki/Manual:Upgrading
  2. Create a complete backup of your MediaWiki database and all files
  3. Test the upgrade in a non-production environment first
  4. Download and install the appropriate fixed version for your branch (1.43.9+, 1.44.6+, 1.45.4+, or 1.46.1+)
  5. Run the MediaWiki update script (maintenance/update.php) to update the database schema
  6. Clear all caches and verify the installation
  7. Test timeline functionality to confirm the fix works correctly
Caveat Minor version upgrades typically have minimal breaking changes; always review the 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58038 — 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-2026-58038 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