blueprintUE Self-Hosted Edition before 4.3.4 Non-Expiring Account Confirmation Tokens
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| blueprintue | blueprintue-self-hosted-edition | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Blueprintue | Blueprintue-self-hosted-edition |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.230% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Blueprintue
Blueprintue blueprintue-self-hosted-edition |
|
| Vendors & Products |
Blueprintue
Blueprintue blueprintue-self-hosted-edition |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | blueprintUE Self-Hosted Edition before 4.3.4 Non-Expiring Account Confirmation Tokens | |
| Weaknesses | CWE-613 | |
| References |
|
|
| Metrics |
cvssV3_1
|