Unauthorized requests via missing CSRF tokens
Published Oct 29, 2025 · Updated Oct 29, 2025
Cross-site request forgery in Azure Access Technology BLU-IC2 and BLU-IC4 through 1.19.5 allows attackers to submit unauthorized requests. The published description identifies a systemic omission of CSRF tokens but does not name the affected endpoints or request handlers. The vendor does not disclose the request trigger or specific controller operations an attacker can invoke, so the precise operational consequence remains undisclosed.
Summary
What happened
Cross-site request forgery in Azure Access Technology BLU-IC2 and BLU-IC4 through 1.19.5 allows attackers to submit unauthorized requests. The published description identifies a systemic omission of CSRF tokens but does not name the affected endpoints or request handlers. The vendor does not disclose the request trigger or specific controller operations an attacker can invoke, so the precise operational consequence remains undisclosed.
The record
- CVE
- CVE-2025-12479
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- Azure Access Technology
- Product
- BLU-IC4
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.19.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo