Skip to main content
VulnerabilityPublished

CVE-2025-12479: Azure Access Technology BLU-IC2 · Cross-Site Request Forgery (CSRF)

Affects Azure Access Technology BLU-IC2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.

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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Azure Access Technology BLU-IC2Affected
  • =0
  • <=1.19.5
Fixed in–

AI-suggested

  1. Implement immediate compensating controls such as web application firewalls (WAFs) configured to detect and block CSRF attack patterns and suspicious cross-origin requests.
  2. Enforce strict validation of the Origin and Referer HTTP headers to ensure requests originate from trusted sources.
  3. Apply session management best practices, including setting SameSite cookie attributes to 'Strict' or 'Lax' to limit cookie transmission in cross-site contexts.
  4. Conduct thorough code reviews and security testing to identify and add CSRF tokens or anti-CSRF mechanisms in all state-changing endpoints.
  5. Monitor logs and user activity for anomalous behavior indicative of CSRF exploitation attempts.
  6. Engage with Azure Access Technology to obtain patches or updates as soon as they become available and prioritize their deployment.
  7. Educate developers and security teams on CSRF risks and secure coding practices to prevent similar vulnerabilities.
  8. Limit the exposure of the affected products to only necessary network segments and restrict access via network segmentation and zero trust principles.
  9. 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 .

References

Community reviews

Loading reviews…