Security readout for executives and security teams
Plain-English summary
Wekan versions before 9.32 can let an attacker attach their OIDC login to an existing Wekan account if the email or username matches. The flaw can result in account takeover, including privileged accounts, because Wekan did not verify ownership of the identity claim before merging accounts.
Executive priority
Treat this as urgent for any Wekan environment using OIDC. The business risk is account takeover without a password compromise, potentially affecting boards, projects, and administrative access. Upgrade to 9.32 should be prioritized over routine maintenance.
Technical view
In server/models/users.js, Wekan's Accounts.onCreateUser hook merged OIDC identities into existing users based on matching email or username without verifying email ownership or checking email_verified. A crafted or permissive OIDC identity could be linked to a victim account. The issue is fixed in Wekan 9.32.
Likely exposure
Highest exposure is Wekan deployments before 9.32 with OIDC login enabled, especially where providers may send unverified or attacker-controlled email or username claims. Deployments without OIDC use have less apparent exposure from the described attack path, but should still upgrade if affected.
Exploitation context
The bundle does not show KEV listing or confirmed active exploitation. The advisory describes unauthenticated network exploitation with low complexity once attack requirements are met: the attacker needs an OIDC account presenting a victim email or username that Wekan accepts for account merging.
Researcher notes
Evidence is limited to the CVE bundle, GitHub advisory, fixing commit, and v9.32 release reference. Do not assume broader product impact or exploitation in the wild from this data. Focus validation on OIDC-enabled Wekan before 9.32 and suspicious account-linking events.
Mitigation direction
- Upgrade Wekan to version 9.32 or later.
- Review the GitHub advisory and v9.32 release notes.
- If upgrade is delayed, review vendor guidance before relying on compensating controls.
- Restrict OIDC to trusted providers and validated identity claims where operationally possible.
- Review privileged accounts for unexpected linked OIDC identities.
Validation and detection
- Inventory all Wekan instances and record installed versions.
- Confirm whether OIDC authentication is enabled on each instance.
- Identify instances running versions earlier than 9.32.
- Review admin and high-value accounts for unexpected OIDC login associations.
- Check authentication logs for unusual first-time OIDC logins to existing accounts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-52893 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wekan/wekan/security/advisories/GHSA-mp7g-hj5q-gxhqCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/wekan/wekan/commit/73204d4e0a7d77a1b186b3d76e8eaf2f3e7c9fd9CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/wekan/wekan/releases/tag/v9.32CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.