dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-56774

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-25
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available 8 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
Kanboard through 1.2.52, fixed in commit 928c68a, UserViewController::removeSession fails to validate the session id parameter before passing it to RememberMeSessionModel::remove, allowing authenticated users to delete other users' Remember Me sessions. Attackers can enumerate sequential session IDs and mass-invalidate persistent login sessions of any user, including administrators, forcing re-authentication and causing denial of service.

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
How this class of weakness works · CWE-639

The application uses a user-supplied identifier to look up a record without checking that the requester actually owns it, so changing the identifier in a request returns someone else's data. This is the classic insecure-direct-object-reference — the change-the-ID-in-the-URL bug. Remediation is authorizing every object access against the acting user, not merely confirming they are logged in.

General guidance for the authorization bypass (idor) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix Moderate confidence

Upgrade to the latest stable Kanboard release (version newer than 1.2.52) that includes commit 928c68a

  1. 1. Identify the current Kanboard version by checking the file 'app/Version.php' or the admin dashboard.
  2. 2. Navigate to the Kanboard GitHub releases page to find the version that includes the fix from commit 928c68a.
  3. 3. If a stable release version (newer than 1.2.52) containing the fix is available, download the upgrade package from the official repository.
  4. 4. Back up the Kanboard database and all configuration files before upgrading.
  5. 5. Deploy the new version by replacing the application files, preserving the config.php file.
  6. 6. Verify the upgrade was successful by checking the version number in the admin interface.
  7. 7. Test that user login and 'Remember Me' functionality works correctly after the upgrade.
Caveat Review release notes for any breaking changes between 1.2.52 and the target version, particularly around session management and authentication features

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

We can apply and verify the patch for your build — typical engagement from $1,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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