dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-52893

CRITICAL · 9.2 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

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 · unedited
Wekan is open source kanban built with Meteor. Prior to 9.32, the Wekan Accounts.onCreateUser hook in server/models/users.js merges OIDC logins into existing accounts when the OIDC email or username matches an existing Wekan user, without verifying ownership or checking email_verified. An attacker using an OIDC provider account with a victim's email or username can cause Wekan to merge the attacker's OIDC credentials into the victim account and then log in as that account. This issue is fixed in version 9.32.

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 confidence

Wekan versions prior to 9.32 have a critical authentication bypass vulnerability in the Accounts.onCreateUser hook. When OIDC login occurs, the system automatically merges OIDC credentials into existing user accounts if the email or username matches, without verifying ownership or checking the email_verified flag. This allows an attacker with an OIDC account using a victim's email/username to inherit full access to the victim's Wekan account.

MitigationUpgrade Wekan to version 9.32 or later to obtain the patch that adds proper ownership verification and email_verified checking before merging OIDC credentials into existing accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Wekan version
    Locate the installed Wekan version through the admin UI (typically in Settings or About section) or by checking the package manager if self-hosted
    Affected if The installed version is below 9.32 (any version from initial release up to 9.31)
  2. Verify OIDC authentication is enabled
    Inspect the Wekan authentication configuration settings to confirm that OIDC (OpenID Connect) login method is active
    Affected if OIDC authentication is enabled in the Wekan authentication settings
  3. Identify existing user accounts
    Review the user account list in the Wekan admin panel to determine if local accounts exist
    Affected if There are user accounts created in Wekan (particularly those created before OIDC was enabled)
  4. Check for email/username overlap potential
    Examine whether the OIDC identity provider's user base contains email addresses or usernames that match existing Wekan local accounts
    Affected if There is any possibility of email or username collision between OIDC users and existing local Wekan accounts

You are affected if you are running any Wekan version below 9.32 with OIDC authentication enabled, as this creates the condition where an attacker with a matching OIDC account can gain unauthorized access to existing local accounts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Wekan to version 9.32 or later to obtain the patch that adds proper ownership verification and email_verified checking before merging OIDC credentials into existing accounts.

Recommended fix High confidence

Wekan version 9.32

  1. Backup your Wekan installation and database before upgrading
  2. Upgrade Wekan to version 9.32 or later
  3. After upgrade, verify that OIDC authentication properly checks email_verified before merging accounts
  4. Test OIDC login flow to confirm the vulnerability is remediated
  5. Ensure existing users cannot have OIDC credentials merged without proper ownership verification

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52893 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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