Allegra calculateTokenExpDate Password Recovery Authentication Bypass Vulnerability

published 2025-06-21 last yr. modified 2026-06-17 4mo ago also EUVD-2025-28704

cvss: 9.8; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 47.8%; EPSS 47.8% chance of exploitation in 30 days, percentile 98%
public exploits: 0; none known

Allegra calculateTokenExpDate Password Recovery Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of Allegra. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the password recovery mechanism. The issue results from reliance upon a predictable value when generating a password reset token. An attacker can leverage this vulnerability to bypass authentication on the application. Was ZDI-CAN-27104.

Patch / fix

fixed in 1

alltena allegra 7.5.2.70, 8.1.24

Is CVE-2025-6216 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: last yr. (2025-06-23)

Exploit prediction

47.78% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Allegra Allegra

Classification

Weakness

CWE-640 Weak Password Recovery Mechanism for Forgotten Password

References

alltena.com /en/resources/release-notes/release-notes-for-release-8-1-4-and-release-7-5-2
vendor-advisory
zerodayinitiative.com /advisories/ZDI-25-410/
third-party-advisory

Sources

CVE List CVE-2025-6216
NVD CVE-2025-6216

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

json critical feed