CVE-2025-62527 json
Taguette vulnerable to password reset link poisoning
published 2025-10-20 12 mo ago modified 2026-10-08 31 d ago also GHSA-7rc8-5c8q-jr6j , PYSEC-2025-187 , EUVD-2025-35097
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
Taguette is an open source qualitative research tool. An issue has been discovered in Taguette versions prior to 1.5.0. It was possible for an attacker to request password reset email containing a malicious link, allowing the attacker to set the email if clicked by the victim. This issue has been patched in version 1.5.0.
Patch / fix
- pypi taguette 1.5.0, 1.5.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12 mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N |
| OSV | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | taguette | <1.5.0 <1.5.1 |
1.5.0 1.5.1 |
Affected products
- remram44 taguette
Classification
- Weakness
-
- CWE-15 External Control of System or Configuration Setting
References
-
github.com
/remram44/taguette/security/advisories/GHSA-7rc8-5c8q-jr6j
web, issue-tracking, vendor-advisory, report
-
gitlab.com
/remram44/taguette/-/issues/331
web, issue-tracking, vendor-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2025-62527
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/taguette/PYSEC-2025-187.yaml
web
-
github.com
/remram44/taguette
package
Sources
- CVE List CVE-2025-62527
- GitHub Advisory GHSA-7rc8-5c8q-jr6j
- NVD CVE-2025-62527
- OSV PYSEC-2025-187
Fencer Vulns 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.