CVE-2025-12479: Azure Access Technology BLU-IC2 · Cross-Site Request Forgery (CSRF)
Affects Azure Access Technology BLU-IC2Source CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 20 Nov 2026, 17:34 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Azure Access Technology BLU-IC2 | Affected
| Fixed in– |
AI-suggested
- Implement immediate compensating controls such as web application firewalls (WAFs) configured to detect and block CSRF attack patterns and suspicious cross-origin requests.
- Enforce strict validation of the Origin and Referer HTTP headers to ensure requests originate from trusted sources.
- Apply session management best practices, including setting SameSite cookie attributes to 'Strict' or 'Lax' to limit cookie transmission in cross-site contexts.
- Conduct thorough code reviews and security testing to identify and add CSRF tokens or anti-CSRF mechanisms in all state-changing endpoints.
- Monitor logs and user activity for anomalous behavior indicative of CSRF exploitation attempts.
- Engage with Azure Access Technology to obtain patches or updates as soon as they become available and prioritize their deployment.
- Educate developers and security teams on CSRF risks and secure coding practices to prevent similar vulnerabilities.
- Limit the exposure of the affected products to only necessary network segments and restrict access via network segmentation and zero trust principles.
- Prepare incident response plans specifically addressing CSRF attack scenarios to enable rapid containment and remediation.
Description
Systemic Lack of Cross-Site Request Forgery (CSRF) Token Implementation.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .