TableProgressTracking's missing CSRF protection allows unauthorized state changes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Telepedia | TableProgressTracking | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Telepedia | Tableprogresstracking | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.123% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Telepedia
Telepedia tableprogresstracking |
|
| Vendors & Products |
Telepedia
Telepedia tableprogresstracking |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | TableProgressTracking's missing CSRF protection allows unauthorized state changes | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV3_1
|