CVE-2026-52892
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 · uneditedWekan is open source kanban built with Meteor. Prior to 9.32, Wekan REST handlers in server/models/customFields.js use read-level Authentication.checkBoardAccess instead of write-level Authentication.checkBoardWriteAccess for mutating custom-field routes. A read-only board member can call POST, PUT, and DELETE handlers for /api/boards/:boardId/custom-fields and custom-field dropdown items to create, update, or delete board custom fields. 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 confidenceWekan's REST API handlers for custom fields in server/models/customFields.js incorrectly use read-level Authentication.checkBoardAccess instead of write-level Authentication.checkBoardWriteAccess. This allows authenticated read-only board members to create, update, or delete board custom fields via POST, PUT, and DELETE requests to /api/boards/:boardId/custom-fields endpoints.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify Wekan versionCheck the installed Wekan version by inspecting the application (e.g., check the Docker image tag, package.json version field, or the Wekan About page in the UI)Affected if the installed version is older than 9.32 (the fixed release)
-
Confirm custom fields feature is in useQuery the database or API to list custom fields: GET /api/boards/:boardId/custom-fields (or check if any boards have custom fields defined in the database)Affected if custom fields exist on any board in the system
-
Check for read-only board membersReview board membership settings to identify users assigned as 'read-only' members (not full members with write access)Affected if any boards with custom fields have read-only member assignments
-
Verify REST API accepts write requests from read-only usersAs a test, attempt a POST, PUT, or DELETE request to /api/boards/:boardId/custom-fields using credentials of a read-only member; inspect the HTTP response codeAffected if the request succeeds (returns 200/204 instead of 401/403)
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 · scopedUpgrade Wekan to version 9.32 or later, which implements proper write-level authorization checks on mutating custom-field REST routes.
Wekan version 9.32
- 1. Identify the current Wekan version by checking the Wekan application or deployment configuration
- 2. Create a complete backup of the Wekan database and configuration files before upgrading
- 3. Upgrade Wekan to version 9.32 or later
- 4. After upgrade, verify that custom-field API endpoints (POST, PUT, DELETE /api/boards/:boardId/custom-fields) now properly require write-level board access
- 5. Test that read-only board members can no longer create, update, or delete custom fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52892 — 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-2026-52892 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