blueprintUE Self-Hosted Edition before 4.3.4 Non-Expiring Account Confirmation Tokens
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.3.4.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
CVE-2026-121735 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects blueprintue-self-hosted-edition; fixed in 4.3.4.
- 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? →
- 23/100 · provisional
- Fix
- Fixed in 4.3.4
- 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
Summary
blueprintUE Self-Hosted Edition, prior to version 4.3.4, is affected. Account confirmation links never expire, so anyone who obtains an old confirmation link, such as from a compromised mailbox, backup, or forwarded email, can activate an unconfirmed account and keep it from being automatically removed.
Read the original description
blueprintUE self-hosted edition before 4.3.4 contains an insufficient session expiration vulnerability that allows attackers to confirm accounts using stale tokens because UserModel::findUserIDWithConfirmedToken ignores confirmed_sent_at. Attackers who obtain an old confirmation link from a compromised mailbox, backup, or forwarded mail can activate unconfirmed accounts and evade the unconfirmed-account cleanup job.
What to do
Upgrade to a fixed version: 4.3.4.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- blueprintue blueprintue-self-hosted-edition
fixed in 4.3.4
Evidence 7
- Advisory
- Patch
- Patch
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121735
Is CVE-2026-121735 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. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-121735?
blueprintue-self-hosted-edition: before 4.3.4.Source: cve.now feed data
How do I fix CVE-2026-121735?
Upgrade to a fixed version: 4.3.4.Source: cve.now feed data