Debian LinuxOperating system · Debian
CVE-2017-0362
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 · uneditedMediawiki before 1.28.1 / 1.27.2 / 1.23.16 contains a flaw where the "Mark all pages visited" on the watchlist does not require a CSRF token.
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 confidenceMediaWiki versions before 1.28.1/1.27.2/1.23.16 have a CSRF vulnerability in the watchlist feature where the 'Mark all pages visited' action does not require a CSRF token, allowing attackers to silently force authenticated users to mark all watched pages as visited via malicious requests.
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
Debian LinuxOperating system
= 7.0>= 1.23.0, <= 1.23.16>= 1.27.0, < 1.27.2>= 1.28.0, < 1.28.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the MediaWiki installationIdentify the webroot directory where MediaWiki is installed. Look for the 'includes/Defines.php' file or the 'composer.json' file which typically contain version information.Affected if Cannot determine version - MediaWiki may still be present but version file not found in expected location
-
Determine the installed MediaWiki versionOpen the includes/Defines.php file and locate the $wgVersion variable, or check composer.json for the version field. Alternatively, access the Special:Version page on the wiki if you have admin access.Affected if The version number is within these ranges: 1.23.0 to 1.23.16, 1.27.0 to 1.27.1, or 1.28.0 to 1.28.0
-
Verify the watchlist feature is accessibleConfirm that authenticated users have access to the watchlist functionality. Visit Special:Watchlist or the watchlist tab on the wiki while logged in as a regular user.Affected if Users can access and use the watchlist feature - the CSRF vulnerability requires an authenticated user session to be exploitable
-
Check for the CSRF token requirement in the markallvisited actionInspect the includes/specials/SpecialWatchlist.php file around the markallvisited function. Look for whether the 'wpEditToken' or CSRF token validation is performed before processing the request.Affected if The markallvisited action lacks CSRF token validation - the code does not verify a token before processing the request
You are affected if your MediaWiki version falls within 1.23.0-1.23.16, 1.27.0-1.27.1, or 1.28.0-1.28.0 AND authenticated users can access the watchlist feature.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.27.21.28.1
Upgrade MediaWiki to version 1.28.1, 1.27.2, 1.23.16 or later which include CSRF token validation for this action.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-0362 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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