SportsTeams Extension up to 1.35.11/1.39.4/1.40.0 on MediaWiki cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in SportsTeams Extension up to 1.35.11/1.39.4/1.40.0 on MediaWiki. Impacted is an unknown function. The manipulation results in cross-site request forgery. This vulnerability is cataloged as CVE-2023-45374. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in SportsTeams Extension up to 1.35.11/1.39.4/1.40.0 on MediaWiki. Affected is an unknown code block. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
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.
The weakness was shared 10/09/2023. The advisory is available at gerrit.wikimedia.org. This vulnerability is traded as CVE-2023-45374 since 10/09/2023. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
Upgrading to version 1.35.12, 1.39.5 or 1.40.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-49666). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 1.0
- 1.1
- 1.2
- 1.3
- 1.4
- 1.5
- 1.6
- 1.7
- 1.8
- 1.9
- 1.10
- 1.11
- 1.12
- 1.13
- 1.14
- 1.15
- 1.16
- 1.17
- 1.18
- 1.19
- 1.20
- 1.21
- 1.22
- 1.23
- 1.24
- 1.25
- 1.26
- 1.27
- 1.28
- 1.29
- 1.30
- 1.31
- 1.32
- 1.33
- 1.34
- 1.35
- 1.35.0
- 1.35.1
- 1.35.2
- 1.35.3
- 1.35.4
- 1.35.5
- 1.35.6
- 1.35.7
- 1.35.8
- 1.35.9
- 1.35.10
- 1.35.11
- 1.36
- 1.37
- 1.38
- 1.39
- 1.39.0
- 1.39.1
- 1.39.2
- 1.39.3
- 1.39.4
- 1.40.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: SportsTeams Extension 1.35.12/1.39.5/1.40.1
Timeline
10/09/2023 🔍10/09/2023 🔍
10/09/2023 🔍
02/09/2026 🔍
Sources
Advisory: gerrit.wikimedia.orgStatus: Confirmed
CVE: CVE-2023-45374 (🔍)
GCVE (CVE): GCVE-0-2023-45374
GCVE (VulDB): GCVE-100-241554
EUVD: 🔍
Entry
Created: 10/09/2023 09:07Updated: 02/09/2026 19:04
Changes: 10/09/2023 09:07 (39), 10/27/2023 15:00 (11), 09/19/2024 20:50 (16), 04/21/2025 14:33 (3), 02/09/2026 19:04 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.