Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. @budibase/server
  4. ›
  5. GHSA-cr7p-cr3q-h5cm

GHSA-cr7p-cr3q-h5cm: Budibase: Account Enumeration via Login Lockout Response Differential

July 24, 2026

The login lockout mechanism in Budibase creates an observable response discrepancy that allows unauthenticated attackers to enumerate valid email addresses. When an existing user’s account is locked after 5 failed login attempts, the server returns a distinct 403 response with X-Account-Locked: 1 and Retry-After: 900 headers plus the message “Account temporarily locked.” For non-existing users, the response is always a generic 403 "Unauthorized" regardless of attempt count, because the lockout counter is never incremented.

References

  • github.com/Budibase/budibase/commit/eaae816ab81615c07eb10e4619af078d00e2a706
  • github.com/Budibase/budibase/pull/19108
  • github.com/Budibase/budibase/releases/tag/3.39.25
  • github.com/Budibase/budibase/security/advisories/GHSA-cr7p-cr3q-h5cm
  • github.com/advisories/GHSA-cr7p-cr3q-h5cm

Code Behaviors & Features

Detect and mitigate GHSA-cr7p-cr3q-h5cm with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions up to 3.38.1

Solution

Unfortunately, there is no solution available yet.

Impact 5.3 MEDIUM

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

Learn more about CVSS

Weakness

  • CWE-204: Observable Response Discrepancy

Source file

npm/@budibase/server/GHSA-cr7p-cr3q-h5cm.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sat, 08 Aug 2026 00:19:21 +0000.