dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-53444

HIGH · 7.6 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 →
82/100
Remediation priority · High
Remotely reachable 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, Wekan OIDC-related Meteor methods in packages/wekan-oidc/oidc_server.js, server/models/org.js, and server/models/team.js are globally callable without the admin authorization checks used by their non-OIDC counterparts. Authenticated users can call setCreateOrgFromOidc, setOrgAllFieldsFromOidc, setCreateTeamFromOidc, setTeamAllFieldsFromOidc, boardRoutineOnLogin, or groupRoutineOnLogin to create or modify organizations and teams, and groupRoutineOnLogin can grant global admin privileges when PROPAGATE_OIDC_DATA is enabled. 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 OIDC-related Meteor methods in oidc_server.js, org.js, and team.js that lack admin authorization checks present in their non-OIDC counterparts. Authenticated users can call methods like setCreateOrgFromOidc, setOrgAllFieldsFromOidc, setCreateTeamFromOidc, setTeamAllFieldsFromOidc, boardRoutineOnLogin, or groupRoutineOnLogin to create/modify organizations and teams without proper authorization. When PROPAGATE_OIDC_DATA is enabled, groupRoutineOnLogin can also grant global admin privileges.

MitigationUpgrade to Wekan version 9.32 or later to obtain the fixed OIDC methods with proper admin authorization checks.

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

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/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. Identify Wekan version
    Check the installed Wekan version (typically found in the application UI footer, in the package.json file, or via the '/api/version' endpoint if available). Compare it against the affected range: versions prior to 9.32 are vulnerable.
    Affected if Installed version is 9.31 or earlier (less than 9.32)
  2. Determine if OIDC authentication is enabled
    Inspect the Wekan configuration files (such as settings.json or environment variables) for OIDC-related settings. Look for OIDC provider configuration sections or the presence of OIDC environment variables (OIDC_<provider>_..., or ROOT_URL combined with OIDC settings).
    Affected if OIDC authentication is configured and enabled in the Wekan deployment
  3. Verify if PROPAGATE_OIDC_DATA setting is active
    Examine the Wekan configuration for the PROPAGATE_OIDC_DATA setting. Check both configuration files and environment variables to determine if this flag is set to true or enabled.
    Affected if PROPAGATE_OIDC_DATA is enabled in the configuration (this allows the most severe impact - granting global admin privileges)
  4. Confirm authenticated user access to OIDC methods
    Verify that authenticated (non-admin) users can access the Meteor methods. The vulnerable methods are setCreateOrgFromOidc, setOrgAllFieldsFromOidc, setCreateTeamFromOidc, setTeamAllFieldsFromOidc, boardRoutineOnLogin, and groupRoutineOnLogin in the OIDC modules.
    Affected if Authenticated users can invoke these OIDC methods without admin-level authorization checks

You are affected if you run Wekan version 9.31 or earlier with OIDC authentication enabled, as authenticated users can exploit the missing admin authorization in OIDC methods to create/modify organizations, teams, or potentially grant global admin privileges when PROPAGATE_OIDC_DATA is set.

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 to Wekan version 9.32 or later to obtain the fixed OIDC methods with proper admin authorization checks.

Recommended fix High confidence

9.32

  1. 1. Backup your current Wekan installation and database before proceeding with any upgrade.
  2. 2. Upgrade Wekan to version 9.32 or later.
  3. 3. After upgrading, verify that the OIDC methods in packages/wekan-oidc/oidc_server.js, server/models/org.js, and server/models/team.js now require proper admin authorization.
  4. 4. Review user accounts that may have gained unauthorized privileges during the vulnerable period and revoke any inappropriate admin grants.
  5. 5. If PROPAGATE_OIDC_DATA was enabled, audit the OIDC configuration to ensure no unintended privilege escalation occurred.
  6. 6. Test the OIDC login flow to confirm normal functionality is preserved after the upgrade.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53444 — 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-53444 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