Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-95654 – Authorization Bypass / Account Takeover – Databasement before 1.7.14

Be the first to know when new zero-days emerge:

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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge