CVE-2025-67646
BaseFortify
Publication date: 2025-12-11
Last updated on: 2025-12-11
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mediawiki | tableprogresstracking | 1.2.0 |
| mediawiki | tableprogresstracking | 1.2.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
To detect this vulnerability on your system, you should check the version of the TableProgressTracking MediaWiki extension installed. Versions 1.2.0 and below are vulnerable, while version 1.2.1 and above include the patch. You can verify the installed version by inspecting the extension.json file in the extension directory or by using MediaWiki's Special:Version page if available. Additionally, monitoring REST API requests to the TableProgressTracking endpoints for missing CSRF tokens can help identify exploitation attempts. However, no specific detection commands are provided in the available resources. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized modification of progress tracking data through CSRF attacks, which could lead to integrity issues in user data. While there is no direct impact on confidentiality or availability, the unauthorized changes may affect compliance with standards that require data integrity and protection against unauthorized actions, such as GDPR and HIPAA. However, the provided resources do not explicitly discuss compliance implications. [2]
Can you explain this vulnerability to me?
This vulnerability exists in the TableProgressTracking MediaWiki extension versions 1.2.0 and below, where the REST API does not enforce CSRF token validation. This allows an attacker to create a malicious webpage that, when visited by an authenticated user, can cause unintended authenticated actions such as deleting or tracking progress against tables without the user's consent.
How can this vulnerability impact me? :
If you use the vulnerable version of the TableProgressTracking extension, an attacker could exploit this vulnerability to perform unauthorized actions on your wiki through an authenticated user's browser. This could lead to deletion or unauthorized modification of progress tracking data in tables, potentially disrupting your wiki's data integrity.
What immediate steps should I take to mitigate this vulnerability?
Upgrade the TableProgressTracking MediaWiki extension to version 1.2.1 or later, as this version includes the patch that enforces CSRF token validation in the REST API, preventing unauthorized actions.