CVE-2025-59480
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 · uneditedMattermost Mobile Apps versions <=2.32.0 fail to verify that SSO redirect tokens originate from the trusted server, which allows a malicious Mattermost instance or on-path attacker to obtain user session credentials via crafted token-in-URL responses
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 confidenceMattermost Mobile Apps versions 2.32.0 and earlier fail to validate that SSO redirect tokens originate from the trusted server, allowing a malicious Mattermost instance or on-path attacker to inject crafted token-in-URL responses and hijack user session credentials.
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< 2.33.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Check Mattermost Mobile app versionOpen the Mattermost mobile app, go to Settings > About > Version (or equivalent), or check the app version displayed in your device's app store listing or installed apps sectionAffected if The displayed version is 2.32.0 or earlier, or any version below 2.33.0
-
Confirm SSO authentication is configuredVerify that the Mattermost server(s) you connect to use SSO-based authentication (such as SAML, OAuth, or OpenID Connect) rather than pure email/password authentication. Check with your server administrator if unsure.Affected if SSO authentication is enabled and used to log into Mattermost servers from this mobile app
-
Check for token-in-URL behaviorDuring SSO login flow on the mobile app, observe if the callback URL contains authentication tokens as URL parameters (tokens appearing after '?token=' or '&token=' in the redirect URL). This is visible in app logs or network traffic if debugging is enabled.Affected if Authentication tokens are passed via URL parameters rather than through secure POST body or dedicated authentication headers
You are affected if your Mattermost Mobile app version is below 2.33.0 AND you use SSO authentication to connect to Mattermost servers, as the app fails to validate that SSO redirect tokens come from the trusted server origin.
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.
dbcve · scoped2.33.0
Upgrade Mattermost Mobile Apps to a version higher than 2.32.0 which implements proper server origin validation for SSO redirect tokens.
Mattermost Mobile 2.33.0 or later
- Open Google Play Store (Android) or App Store (iOS) on the mobile device
- Search for 'Mattermost' or locate the installed Mattermost Mobile app
- Tap 'Update' to install version 2.33.0 or later
- After updating, open the app and verify the version number in Settings > About to confirm 2.33.0 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59480 — 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-2025-59480 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