CVE-2025-67646
Unknown Unknown - Not Provided

BaseFortify

Publication date: 2025-12-11

Last updated on: 2025-12-11

Assigner: GitHub, Inc.

Description
TableProgressTracking is a MediaWiki extension to track progress against specific criterion. Versions 1.2.0 and below do not enforce CSRF token validation in the REST API. As a result, an attacker could craft a malicious webpage that, when visited by an authenticated user on a wiki with the extension enabled, would trigger unintended authenticated actions through the victim's browser. Due to the lack of token validation, an attacker can delete or track progress against tables. This issue is patched in version 1.2.1 of the extension.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2025-12-11
Last Modified
2025-12-11
Generated
2026-07-06
AI Q&A
2025-12-11
EPSS Evaluated
2026-07-05
NVD
CVE-2025-67646

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
mediawiki tableprogresstracking 1.2.0
mediawiki tableprogresstracking 1.2.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Mitigation Strategies

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.

Compliance Impact

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]

Detection Guidance

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]

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-67646. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart