Skip to content
NewA calmer, faster ZeroHour
VulnerabilityKEVPoC ×25

CVE-2021-23758

Unauthenticated .NET Deserialization RCE in Ajax.NET Professional (ajaxpro.2)

CISA: Ajax.NET Professional Deserialization of Untrusted Data Vulnerability

CVSS 3.1
9.8 critical
EPSS
83%p100
Published
·
Added to KEV
Analyze CVE-2021-23758 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

Ajax.NET Professional (distributed as the ajaxpro.2 package) is vulnerable to insecure deserialization (CWE-502): it deserializes arbitrary .NET classes supplied by the client without validating which types may be instantiated. Because AjaxPro exposes HTTP endpoints for browser-to-server AJAX calls, a remote, unauthenticated attacker can send a crafted serialized payload to any reachable AjaxPro endpoint and abuse .NET deserialization gadget chains to execute code on the server. Successful exploitation yields full remote code execution with high impact on confidentiality, integrity, and availability (CVSS 3.1 score of 9.8, network vector, no privileges or user interaction required). Any application running any version of ajaxpro.2 / Ajax.NET Professional is affected; the provided data specifies no fixed version, so defenders must rely on vendor guidance for patched releases. The flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2026-08-26, carries an EPSS 30-day exploitation probability of 83.6%, has public PoC code available, and Talos Intelligence reporting links it to the Chinese-speaking threat actor UAT-10147, which deploys the SPECTRE malware with an EDR bypass and a Linux rootkit in post-compromise operations.

What to do: Inventory your ASP.NET estate for AjaxPro usage (web.config references, AjaxPro HTTP handlers) and prioritize any internet-facing instance for remediation. Upgrade ajaxpro.2 to the latest vendor release per vendor instructions — the provided data specifies no fixed version — or, if patching is not immediately possible, restrict or block access to AjaxPro endpoints from the internet. Because the flaw is on CISA's KEV under BOD 26-04, apply mitigations within the required timeline and hunt exposed servers for post-compromise tooling, as Talos reports UAT-10147 deploying SPECTRE with an EDR bypass and a Linux rootkit.

ProductAffected
michaelschwarz (ajaxpro.2 project) ajaxpro.2 (package)All versions are vulnerable; no fixed version specified in the provided data
michaelschwarz Ajax.NET ProfessionalAll versions are vulnerable; no fixed version specified in the provided data
Estimated exposure
unknown (no public install-base or internet-exposure counts available for this legacy library) — The provided data contains no download counts, active-install figures, or internet-exposed device scan results for the legacy Ajax.NET Professional / ajaxpro.2 library, which is typically embedded in aging ASP.NET applications whose…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

All versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution.

KEVCISA Known Exploited Vulnerability
Affected
Ajax.NET Professional Ajax.NET Professional
Required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Due date
Ransomware use
Unknown
Vendors
ajaxpro.2 projectmichaelschwarz
Products
ajaxpro.2, ajax.net professional
Weakness
CWE-502
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

In the news

4 stories