# CVE-2026-95654: Databasement token validation bypass in invitation acceptance

Source: https://junglewise.ai/threats/cve-2026-95654-databasement-before-1-7-14-validates-invitation-tokens-only-when  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-22. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-95654 · Severity: high · CVSS 7.4 · Published 2026-09-22

Databasement is a self-hosted database backup manager that allows teams to manage database credentials and backups through a web interface. An attacker who obtains a pending invitation link can load the acceptance page while the invitation is valid, then later submit a password change to hijack the account even after the legitimate user has already accepted the invitation. This allows unauthorized access to the managed database credentials and backup data.

Technologies: [David-Crty Databasement](https://junglewise.ai/threats/technologies/databasement). Vendors: [David-Crty](https://junglewise.ai/threats/vendors/david-crty).

## Quick answers

**Is CVE-2026-95654 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-95654 being exploited in the wild.

**How severe is CVE-2026-95654?** High severity, with a CVSS score of 7.4, published 22 September 2026.

**Which products and versions are affected?** David-Crty Databasement before 1.7.14.

**Is there a fix for CVE-2026-95654?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-95654 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-95654?** Check whether you run David-Crty Databasement at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability stems from the mount() method in AcceptInvitation.php validating the invitation token only once when the page loads, but the accept() method does not re-validate the token before updating the user's password. An attacker can load the page with a valid pending token, then submit the form after the token has been invalidated (e.g., when the legitimate user accepts the invitation), successfully overwriting the password and gaining authenticated access. The fix in version 1.7.14 re-validates token validity during the accept action.

## Affected products

- David-Crty Databasement before 1.7.14

## Timeline

- 2026-09-22: disclosed

## References

- [https://github.com/David-Crty/databasement](https://github.com/David-Crty/databasement)
- [https://github.com/David-Crty/databasement/blob/v1.7.13/app/Livewire/Auth/AcceptInvitation.php](https://github.com/David-Crty/databasement/blob/v1.7.13/app/Livewire/Auth/AcceptInvitation.php)

## Related threats

- [Databasement authentication bypass in OAuthService](https://junglewise.ai/threats/cve-2026-121939-databasement-before-1-10-9-contains-an-authentication-bypass)
- [Databasement missing authorization in scheduled restore](https://junglewise.ai/threats/cve-2026-111875-a-vulnerability-has-been-found-in-david-crty-databasement-up-to)
- [databasement argument injection in database backup commands](https://junglewise.ai/threats/cve-2026-108963-databasement-before-1-8-2-allows-remote-code-execution-because)
- [David-Crty databasement improper access control in Snapshot API](https://junglewise.ai/threats/cve-2026-103534-a-vulnerability-was-determined-in-david-crty-databasement-up-to)
- [David-Crty databasement path traversal in RestoreRequest](https://junglewise.ai/threats/cve-2026-103533-a-vulnerability-was-found-in-david-crty-databasement-up-to-1-7-1)