CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Idunno.AntiCsrf

product · product:idunno-anticsrf single-source

Coverage
1
first 2026-11-19 → last 2026-11-19
Latest activity
2026-11-19
Idunno.AntiCsrf (ASP.NET WebForms) unauthenticated deserialization RCE exploited, no patch: remove the module
Peak priority
notable
1 notable
Targets
technology
sectors: technology
Sources cited
2
2 hosts

Action items (1)

Do-now tasks recorded on the entries about Idunno.AntiCsrf, newest first. Check the date before acting on an older one.

  • Search every ASP.NET WebForms application's Web.config and bin directory for Idunno.AntiCsrf by name, not by file hash because recompiled copies keep the flaw, and remove the module and its DLL, replacing it with a supported anti-forgery mechanism; on any server with evidence of exploitation, such as IIS requests to .aspx pages that returned 302 or 500 with unusually large request sizes, rotate the machineKey, encryption keys and database credentials in Web.config and applicationHost.config, because Mandiant observed exploitation and no patch exists.
    2026-11-19CVE-2026-131914

Defender insights

What each entry about Idunno.AntiCsrf tells a defender to do, newest first.

2026-11-19NOTABLEexploitedIdunno.AntiCsrf (ASP.NET WebForms) unauthenticated deserialization RCE exploited, no patch: remove the module

Exposure · triage · detection

Story timeline

  1. 2026-11-19CVE-2026-131914, Idunno.AntiCsrf 0.9.1 and earlier, a defunct anti-CSRF module for ASP.NET WebForms: one unauthenticated POST with a crafted CSRF form field is deserialized without validation and runs code in the IIS worker process; Mandiant observed exploitation in the wild and no patch exists, so the module has to be removed (CVSS 4.0 9.3)
    trending-vulnerabilitiesIdunno.AntiCsrf (ASP.NET WebForms) unauthenticated deserialization RCE exploited, no patch: remove the module

Hunting pivots

CVEs (exploited first)
Releases covered
Idunno.AntiCsrf
ATT&CK techniques (1 across 1 tactic)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-11-19/idunno-anticsrf-cve-2026-131914-exploited-no-patch-w3wp-rce · ATT&CK page ↗

Entries about Idunno.AntiCsrf (1)

2026-11-19 · view entry permalink →

NOTABLECVE-2026-131914exploitedNATOB2

CVE-2026-131914, Idunno.AntiCsrf 0.9.1 and earlier, a defunct anti-CSRF module for ASP.NET WebForms: one unauthenticated POST with a crafted CSRF form field is deserialized without validation and runs code in the IIS worker process; Mandiant observed exploitation in the wild and no patch exists, so the module has to be removed (CVSS 4.0 9.3)

Mandiant published advisory MNDT-2026-0048 and CVE-2026-131914 on 2026-11-18 for Idunno.AntiCsrf, a defunct open-source anti-CSRF HTTP module for ASP.NET WebForms, last released as 0.9.1 Beta in December 2008 on the since-retired CodePlex platform and with no active maintainer or official patch (Mandiant, 2026-11-18). In the module's PreRequestHandlerExecute step, once the CSRF cookie and the CSRF form field are both non-empty, it deserializes the form field with a parameterless ObjectStateFormatter, which performs no MAC, signature, encryption or machineKey validation and enforces no SerializationBinder restrictions, so a crafted serialized .NET object in that field runs code in the IIS worker process, w3wp.exe; one POST with no prior authentication or valid CSRF token suffices (Mandiant, 2026-11-18).

The module runs before the page lifecycle, so any anonymously reachable .aspx page, or any page that relies on application-level session checks inside Page_Load, is reachable unless it opts out through ISuppressCsrfCheck or the SuppressCsrfCheck attribute; pipeline-level authentication rules run earlier and keep anonymous requests away from pages they protect (Mandiant, 2026-11-18). After the sink the module raises its own error, so the response is HTTP 302 when customErrors is active and HTTP 500 when its mode is Off, and recompiled or customised copies keep the sink under different file hashes (Mandiant, 2026-11-18). Mandiant states that active exploitation in the wild has been observed, names no actor, and says Google's FLARE team completed the root-cause analysis during an incident-response investigation on 2026-11-04 (Mandiant, 2026-11-18); the ENISA record scores the flaw CVSS 4.0 9.3 (ENISA EUVD, 2026-11-19).

Triage: the module's own tokens are a GUID cookie and a short serialized GUID in the form field, so a cookie that is not a GUID, or a large Base64 value in the CSRF form field, is not legitimate token traffic (Mandiant, 2026-11-18).

Active exploitation in the wild has been observed.

has no active maintainer or official patch available.

Mandiant Vulnerability Disclosures (MNDT-2026-0048, CNA) 2026-11-18
vulnerability19 Nov 05:16Zsingle-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • euvdservices.enisa.europa.eu1 (50%)
  • github.com1 (50%)