CVE-2026-95654: David-Crty Databasement · Incorrect Authorization
Affects David-Crty DatabasementSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.7.14 as a priority.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.14
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade Databasement and david-crty/databasement to 1.7.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| David-CrtyDatabasement | Affected
| Fixed in
|
GitHubdavid-crty/databasementpkg:github/david-crty/databasementOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Databasement version 1.7.14 and later. Users should upgrade to version 1.7.14 or newer to address this incorrect authorization vulnerability. No other mitigation is indicated in the provided data.
Description
Databasement before 1.7.14 validates invitation tokens only when the acceptance page loads, caching the authorization decision without re-checking token validity during acceptance. Attackers with a leaked or forwarded invitation link can load the page while pending, then accept the invitation after the legitimate user has already accepted it to overwrite the account password and gain authenticated access to managed database credentials and secrets.
References
- github.com/David-Crty/databasement/commit/128efeaf6bc9ad4a63940f4c3030a56ab2969778 (opens in a new tab)
- github.com/David-Crty/databasement/blob/v1.7.13/app/Livewire/Auth/AcceptInvitation.php (opens in a new tab)
- github.com/David-Crty/databasement/blob/v1.7.13/app/Livewire/Auth/AcceptInvitation.php (opens in a new tab)
- github.com/David-Crty/databasement/releases/tag/v1.7.14 (opens in a new tab)
- github.com/David-Crty/databasement (opens in a new tab)
- vulncheck.com/advisories/databasement-before-1.7.14-authorization-bypass-via-stale-invitation-token (opens in a new tab)