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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
blueprintue blueprintue-self-hosted-edition
Default version status: unaffected
0 to < 4.3.4affected
pkg:github/blueprintue/blueprintue-self-hosted-editionReferences
- https://github.com/blueprintue/blueprintue-self-hosted-edition/commit/8bba1615bf76b144ac5cd72637c243490f08bc37 ↗
- https://github.com/blueprintue/blueprintue-self-hosted-edition ↗
- https://github.com/blueprintue/blueprintue-self-hosted-edition/security/advisories/GHSA-qp6g-7v4v-33r9 ↗
- https://github.com/blueprintue/blueprintue-self-hosted-edition/pull/266 ↗
- https://github.com/blueprintue/blueprintue-self-hosted-edition/blob/v4.3.3/app/models/UserModel.php#L361-L368 ↗
- https://github.com/blueprintue/blueprintue-self-hosted-edition/releases/tag/v4.3.4 ↗
- https://www.vulncheck.com/advisories/blueprintue-self-hosted-edition-before-4.3.4-non-expiring-account-confirmation-tokens ↗