Databasement before 1.10.9 Account Takeover via OIDC Email Auto-Linking
Affects Databasement before 1.10.9 when OIDC login is enabled with email auto-linking, which defaults to on. CVSS rates it critical. Fixed in 1.10.9.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 1.10.9
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Exploitation15/40CISA rates a proof of concept as public
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity10/10CVSS 9.2, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
CVE-2026-121939 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.2 (critical) and affects Databasement; fixed in 1.10.9.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 47/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Fix
- Fixed in 1.10.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
Databasement, before the fixed release, can be abused remotely and without logging in: an attacker registers an identity provider account using a victim's unverified email address, and the application links that account to the victim's local user, including the super-admin. The attacker can then take over the account and keep access even after the victim resets their password.
Read the original description
Databasement before 1.10.9 contains an authentication bypass vulnerability in OAuthService::findOrCreateLocalUser() that links OIDC identities to local users by email without checking email_verified. Attackers can register an identity provider account with a victim's unverified email to log in as any user, including the super-admin, and retain access after password resets.
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 1.10.9.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- David-Crty Databasement
fixed in 1.10.9
Evidence 5
- Advisory
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121939
Is CVE-2026-121939 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Email auto-linking lets an OIDC login attach to an existing local account by matching the email address. If the identity provider accepts an unverified email, someone who creates an account there with the victim's email can log in as that victim, including the super-admin account.Source: github.com
Which versions are affected by CVE-2026-121939?
Databasement: before 1.10.9.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 1.10.9 are affected when OIDC login is enabled and auto_link_by_email is on, which is the default. To check a setup, look at the installed Databasement version and at the OIDC login and auto_link_by_email settings.Source: github.com
How do I fix CVE-2026-121939?
Upgrade to Databasement 1.10.9 or later, which contains the fix. The sources provided do not describe a workaround for earlier versions.Source: github.com