Persistent profile access via unrevoked refresh tokens
Published Apr 11, 2025 · Updated Jul 7, 2025
Incorrect authorization in Wikimedia Foundation OAuth 1.39 through 1.43 allows remote authenticated users to retain profile access. The refresh-token validation path checks cache revocation state but fails to verify that the backing access-token database row still exists after grant revocation. A previously authorized, non-owner-only OAuth2 consumer with a retained refresh token can mint replacement tokens and keep reading the user's profile or private email after consent is withdrawn.
Summary
What happened
Incorrect authorization in Wikimedia Foundation OAuth 1.39 through 1.43 allows remote authenticated users to retain profile access. The refresh-token validation path checks cache revocation state but fails to verify that the backing access-token database row still exists after grant revocation. A previously authorized, non-owner-only OAuth2 consumer with a retained refresh token can mint replacement tokens and keep reading the user's profile or private email after consent is withdrawn.
The record
- CVE
- CVE-2025-32068
- Published
- Apr 11, 2025
- Updated
- Jul 7, 2025
- Vendor
- Wikimedia Foundation
- Product
- OAuth
- Classifications
- CWE-863, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 11, 2025CVE publishedPublication date reported by the CVE source.
- Jul 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.39 <=1.43
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo