Summary
CVE-2026-95654 is an incorrect authorization vulnerability (CWE-863) in Databasement, a database credential management platform from David-Crty, affecting all versions prior to 1.7.14. The flaw lets an attacker who obtains a pending invitation link race the legitimate recipient to complete account acceptance, overwrite the account password, and gain authenticated access to the victim’s managed database credentials and secrets. The issue is rated CRITICAL (CVSS v4.0 9.1) / HIGH (CVSS v3.1 7.4) and is remotely exploitable with no privileges and no user interaction from the victim.
Technical details
- Root cause: Databasement validates an invitation token only once, when the invitation acceptance page is first loaded, and caches that authorization decision instead of re-verifying the token’s validity at the moment acceptance is actually submitted.
- Trigger condition: An attacker who has obtained a copy of a still-pending invitation link (e.g., a leaked, forwarded, or intercepted invite URL) loads the acceptance page while the invitation is pending, then submits the acceptance request after the intended recipient has already accepted it.
- Attack vector: Network — no authentication and no victim interaction is required beyond the attacker possessing the invitation link; the request is made directly against the acceptance endpoint.
- Impact: Successful exploitation allows the attacker to overwrite the account’s password and obtain authenticated access to the account, including any database credentials and secrets managed through Databasement.
Affected software
- Databasement (David-Crty) — all versions prior to 1.7.14
Severity
- CVSS v3.1: 7.4 (HIGH) —
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - CVSS v4.0: 9.1 (CRITICAL) —
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade Databasement to version 1.7.14 or later, which re-validates invitation tokens at acceptance time rather than relying on a cached authorization decision.
- If immediate patching is not possible:
- Treat all outstanding invitation links as sensitive credentials; avoid forwarding or exposing them, and revoke/expire pending invitations that are no longer needed.
- Monitor for duplicate or repeated acceptance attempts against the same invitation token.
- Restrict network exposure of the Databasement management interface to trusted networks or VPN until patched.

