dbcve.org
MediawikiCMS

CVE-2023-45370

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. SportsTeams: Special:SportsManagerLogo and Special:SportsTeamsManagerLogo do not check for the sportsteamsmanager user right, and thus an attacker may be able to affect pages that are concerned with sports teams.

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 has a missing authorization check on Special:SportsManagerLogo and Special:SportsTeamsManagerLogo pages. These special pages fail to verify the sportsteamsmanager user right before rendering, allowing any authenticated user to access sports team management functionality they should not have permission to use.

MitigationUpgrade the SportsTeams extension to version 1.35.12, 1.39.5, or 1.40.1 or later which add the required user right checks to the affected special pages.

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. Identify MediaWiki version
    Check your MediaWiki installation version (typically in includes/Defines.php or Special:Version page)
    Affected if Version is < 1.35.12, OR >= 1.36.0 AND < 1.39.5, OR equals 1.40.0
  2. Verify SportsTeams extension is installed
    Check if the SportsTeams extension directory exists in your extensions folder and is loaded in LocalSettings.php
    Affected if The SportsTeams extension is present and active in the MediaWiki installation
  3. Confirm sportsteamsmanager user right exists
    Navigate to Special:ListGroupRights or check $wgGroupPermissions in your configuration to see if the sportsteamsmanager right is defined
    Affected if The sportsteamsmanager right exists in the system but is not being enforced on the affected special pages
  4. Test access to affected special pages
    As a low-privileged authenticated user (without sports team management rights), attempt to access Special:SportsManagerLogo and Special:SportsTeamsManagerLogo
    Affected if These pages load without denying access to users lacking the sportsteamsmanager right

Your environment is affected if you run a vulnerable MediaWiki version with the SportsTeams extension and the special pages are accessible to authenticated users lacking the sportsteamsmanager right.

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 to version 1.35.12, 1.39.5, or 1.40.1 or later which add the required user right checks to the affected special pages.

Recommended fix High confidence

MediaWiki 1.35.12+ (1.35 branch), 1.39.5+ (1.36-1.39 branch), or 1.40.1+ (1.40 branch)

  1. 1. Determine your current MediaWiki version by checking the includes/DefaultSettings.php file or Special:Version page
  2. 2. Identify which version branch you are on (1.35.x, 1.36.x-1.39.x, or 1.40.x)
  3. 3. For 1.35.x branch: upgrade to MediaWiki 1.35.12 or later
  4. 4. For 1.36.x-1.39.x branch: upgrade to MediaWiki 1.39.5 or later
  5. 5. For 1.40.x branch: upgrade to MediaWiki 1.40.1 or later
  6. 6. Ensure the SportsTeams extension is also updated to a compatible version matching your MediaWiki release
  7. 7. After upgrade, verify that Special:SportsManagerLogo and Special:SportsTeamsManagerLogo now properly check for the 'sportsteamsmanager' user right
Caveat Review MediaWiki release notes for your target version for any configuration or compatibility changes; some older extensions may require updates

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-45370 — 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-45370 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