CVE-2025-3230: Bypass of System Admin User Deactivation Controls for Personal Access Tokens in Mattermost Server
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/mattermost/mattermost-server (Go) 10.5.4+incompatible, 10.6.3+incompatible, 10.7.1+incompatible; github.com/mattermost/mattermost/server/v8 (Go) 10.5.4, 10.6.3, 10.7.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250612T141001-1.1.
Low priority for now. Upgrade to github.com/mattermost/mattermost-server (Go) 10.5.4+incompatible, 10.6.3+incompatible, 10.7.1+incompatible; github.com/mattermost/mattermost/server/v8 (Go) 10.5.4, 10.6.3, 10.7.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250612T141001-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Mattermost versions 10.7.x <= 10.7.0, 10.6.x <= 10.6.2, 10.5.x <= 10.5.3, 9.11.x <= 9.11.12 fails to properly invalidate personal access tokens upon user deactivation, allowing deactivated users to maintain full system access by exploiting access token validation flaws via continued usage of previously issued tokens.
- Published
- May 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-303
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.4
- CNA · Mattermost
- 5.4
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mattermost | mattermost server | cpe:2.3:a:mattermost:mattermost_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mattermost mattermost server9.11.0 and later · before 9.11.13
- mattermost mattermost server10.5.0 and later · before 10.5.4
- mattermost mattermost server10.6.0 and later · before 10.6.3
- mattermost mattermost server10.7.0 and later · before 10.7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Mattermost). Independent of NVD's CPE analysis and usually ahead of it.
Mattermost Mattermost
- 10.8.0, 10.7.1, 10.6.3, 10.5.4, 9.11.13not affected
- 10.7.0affected
- 10.6.0 and later · up to and including 10.6.2affected · semver
- 10.5.0 and later · up to and including 10.5.3affected · semver
- 9.11.0 and later · up to and including 9.11.12affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/mattermost/mattermost-server | from 10.0.0-rc1+incompatible · before 10.5.4+incompatible | 10.5.4+incompatible |
| Go | github.com/mattermost/mattermost-server | from 10.6.0-rc1+incompatible · before 10.6.3+incompatible | 10.6.3+incompatible |
| Go | github.com/mattermost/mattermost-server | from 10.7.0-rc1+incompatible · before 10.7.1+incompatible | 10.7.1+incompatible |
| Go | github.com/mattermost/mattermost-server | from 9.0.0-rc1+incompatible · before 9.11.13+incompatible | 9.11.13+incompatible |
| Go | github.com/mattermost/mattermost-server/v5 | from 0 | — |
| Go | github.com/mattermost/mattermost-server/v6 | from 0 | — |
| Go | github.com/mattermost/mattermost/server/v8 | from 10.0.0-rc1 · before 10.5.4 | 10.5.4 |
| Go | github.com/mattermost/mattermost/server/v8 | from 10.6.0-rc1 · before 10.6.3 | 10.6.3 |
| Go | github.com/mattermost/mattermost/server/v8 | from 10.7.0-rc1 · before 10.7.1 | 10.7.1 |
| Go | github.com/mattermost/mattermost/server/v8 | from 9.0.0-rc1 · before 9.11.13 | 9.11.13 |
| Go | github.com/mattermost/mattermost/server/v8 | before 8.0.0-20250402193107-65343f84a783 | 8.0.0-20250402193107-65343f84a783 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250612T141001-1.1 | 0.0.20250612T141001-1.1 |
Same product
mattermost: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-4858Path traversal in integration action URL leading to arbitrary API execution via system admin’s auth token.39Monitor
- CVE-2025-12421Account Takeover via Code Exchange Endpoint39Monitor
- CVE-2025-12419Account takeover on OAuth/OpenID-enabled servers39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-1792May 30, 2025 · Improper Access Control in Mattermost Channel Member API12Monitor
- ← EarlierCVE-2025-2571May 30, 2025 · Google OAuth Authentication Bypass for Converted Bot Accounts16Monitor
- Later →CVE-2025-3611May 30, 2025 · Improper Access Control in Mattermost allows System Managers to view team details despite role restrictions17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/mattermost/mattermost-server | 10.5.4+incompatible | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 10.6.3+incompatible | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 10.7.1+incompatible | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 9.11.13+incompatible | Package registry (OSV) |
| Go:github.com/mattermost/mattermost/server/v8 | 10.5.4 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost/server/v8 | 10.6.3 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost/server/v8 | 10.7.1 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost/server/v8 | 8.0.0-20250402193107-65343f84a783 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost/server/v8 | 9.11.13 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250612T141001-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- eAhmedfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-12419181 days apartAccount takeover on OAuth/OpenID-enabled servers39Monitor
- CVE-2025-12421181 days apartAccount Takeover via Code Exchange Endpoint39Monitor
- CVE-2025-14273206 days apartMattermost Jira plugin user spoofing enables Jira request forgery.33Monitor
- CVE-2026-27656299 days apartAccount Takeover via Substring Matching in OpenID Connect Authentication24Monitor
- CVE-2025-247546 days apartUnauthorized Bot Login Using Credentials21Monitor
- CVE-2024-36250202 days apartMattermost versions 9.11.x <= 9.11.2, and 9.5.x <= 9.5.10 fail to protect the mfa code against replay attacks, which allows an attacker to r19Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-303 · Incorrect Implementation of Authentication AlgorithmCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.