Taiga Blind SQL Injection Time Based

published 2025-10-28 last yr. modified 2026-10-08 last mo. also EUVD-2025-36560

cvss: 4.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits: 0; none known

Taiga is an open source project management platform. In versions 6.8.3 and earlier, Taiga API is vulnerable to time-based blind SQL injection allowing sensitive data disclosure via response timing. This issue is fixed in version 6.9.0.

Is CVE-2025-62367 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: no
Technical impact: partial
Assessed: last yr. (2025-10-28)

Exploit prediction

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

CVSS scores

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

Affected products

taigaio taiga-back

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

github.com /taigaio/taiga-back/security/advisories/GHSA-chm9-9wwq-xffj

Sources

CVE List CVE-2025-62367
NVD CVE-2025-62367

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.