dbcve.org
MediawikiCMS

CVE-2023-45374

MEDIUM · 5.3 CVSS v3.1 Published 2023-10-09
Fix available
A fix is available. Upgrade to 1.35.12 / 1.39.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
An issue was discovered in the SportsTeams extension for MediaWiki before 1.35.12, 1.36.x through 1.39.x before 1.39.5, and 1.40.x before 1.40.1. It does not check for the anti-CSRF edit token in Special:SportsTeamsManager and Special:UpdateFavoriteTeams.

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

The SportsTeams MediaWiki extension lacks anti-CSRF edit token validation on Special:SportsTeamsManager and Special:UpdateFavoriteTeams pages, allowing attackers to craft malicious requests that trick authenticated administrators or users into performing unintended actions like modifying team data or updating favorites.

MitigationUpgrade the SportsTeams extension and MediaWiki core to the patched versions (1.35.12, 1.39.5, or 1.40.1) which add the missing token validation checks.

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.35.12>= 1.36.0, < 1.39.5= 1.40.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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check MediaWiki core version
    Locate the MediaWiki version file (usually includes/Defines.php or autoload.php) or access Special:Version on the wiki. The version is typically displayed at the top of that special page.
    Affected if The installed version falls within < 1.35.12, >= 1.36.0 and < 1.39.5, or equals 1.40.0.
  2. Verify SportsTeams extension is installed
    Check for the SportsTeams extension directory in the MediaWiki extensions folder (usually /extensions/SportsTeams/). Also check the LocalSettings.php file for a line like 'wfLoadExtension( "SportsTeams" );'.
    Affected if The SportsTeams extension directory exists and is loaded in LocalSettings.php.
  3. Confirm vulnerable special pages are accessible
    Attempt to access Special:SportsTeamsManager and Special:UpdateFavoriteTeams while logged in as an administrator or user. These pages exist if the extension is enabled.
    Affected if Both Special:SportsTeamsManager and Special:UpdateFavoriteTeams pages load without errors and do not require authentication.
  4. Inspect CSRF token validation in extension code
    Examine the SportsTeams extension source files for the Special:SportsTeamsManager and Special:UpdateFavoriteTeams handler files. Look for the use of $this->getRequest()->getCheckToken( 'edit' ) or similar edit token validation calls within the handleForm or execute methods.
    Affected if The special page handler files lack edit token validation calls using getCheckToken or requireToken methods.

A user is affected if their MediaWiki version is vulnerable, the SportsTeams extension is installed and enabled, and the extension code lacks edit token validation on the vulnerable special pages.

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.35.12 / 1.39.5 or later
Fixed in 1.35.121.39.5
Interim mitigation

Upgrade the SportsTeams extension and MediaWiki core to the patched versions (1.35.12, 1.39.5, or 1.40.1) which add the missing token validation checks.

Recommended fix Moderate confidence

MediaWiki 1.35.12, 1.39.5, or 1.40.1 (depending on your current branch)

  1. 1. Identify the current MediaWiki version running in your environment
  2. 2. For MediaWiki < 1.35.12: Upgrade to MediaWiki 1.35.12 or later
  3. 3. For MediaWiki 1.36.x - 1.39.x: Upgrade to MediaWiki 1.39.5 or later
  4. 4. For MediaWiki 1.40.0: Upgrade to MediaWiki 1.40.1 or later
  5. 5. After upgrade, verify the SportsTeams extension is updated to include the CSRF token validation fix
  6. 6. Test the Special:SportsTeamsManager and Special:UpdateFavoriteTeams special pages to confirm functionality
Caveat Review MediaWiki release notes for your target version for any configuration or compatibility changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mediawiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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