OWASP AntiSamy .NET is a library for performing cleansing of HTML coming from untrusted sources. Prior to version 1.2.0, there is a potential for a mutation cross-site scripting (mXSS) vulnerability in AntiSamy caused by flawed parsing of the HTML being sanitized. To be subject to this vulnerability the preserveComments directive must be enabled in your policy file and also allow for certain tags at the same time. As a result, certain crafty inputs can result in elements in comment tags being interpreted as executable when using AntiSamy's sanitized output. This is patched in OWASP AntiSamy .NET 1.2.0 and later. See important remediation details in the reference given below. As a workaround, manually edit the AntiSamy policy file (e.g., antisamy.xml) by deleting the preserveComments directive or setting its value to false, if present. Also it would be useful to make AntiSamy remove the noscript tag by adding a line described in the GitHub Security Advisory to the tag definitions under the `` node, or deleting it entirely if present. As the previously mentioned policy settings are preconditions for the mXSS attack to work, changing them as recommended should be sufficient to protect you against this vulnerability when using a vulnerable version of this library. However, the existing bug would still be present in AntiSamy or its parser dependency (HtmlAgilityPack). The safety of this workaround relies on configurations that may change in the future and don't address the root cause of the vulnerability. As such, it is strongly recommended to upgrade to a fixed version of AntiSamy.
CVE-2023-51652
“—” beside the score: it is equal to NVD's CVSS score.
This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.1
- EG Score
- 6.1MEDIUMmedium confidence
- EG Risk
- 28EG Risk 28/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity61% × 45%The EG Score, 6.1 of 10.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 37th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
January 2, 2024
Last Modified
June 17, 2026
References (3)
- security-advisories@github · CVE Programhttps://github.com/spassarop/antisamy-dotnet/commit/7e500daef6ad9c10e97c68feab78f4cb6e3083c6Patch
- security-advisories@github · CVE Programhttps://github.com/spassarop/antisamy-dotnet/commit/8117911933e75a25cd0054ef017577486338444aPatch
- security-advisories@github · CVE Programhttps://github.com/spassarop/antisamy-dotnet/security/advisories/GHSA-8x6f-956f-q43wVendor Advisory
Affected Packages
(1 across 1 ecosystem)
NuGet(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| OWASP.AntiSamy | 1.0.0 ... 1.1.1 (6 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 33× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 89 of 191 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-12 18:14 UTCEG score recompute
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-12 07:54 UTCOSV refresh
- 2026-10-11 21:39 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-30 16:36 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 38th percentile
Show 64 moreShow fewer
- 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-09-22 11:46 UTCOSV refresh
- 2026-09-21 20:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-09-17 19:25 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-03 09:00 UTCOSV refresh
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-09-01 04:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-16 22:26 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-10 23:57 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-08-01 16:36 UTCOSV refresh
- 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-27 14:10 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-07-23 02:29 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-79
Frequently asked(5)
What is CVE-2023-51652?
When was the CVE record for CVE-2023-51652 published?
Is CVE-2023-51652 actively exploited?
What is the CVSS score of CVE-2023-51652?
How do I remediate CVE-2023-51652?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-51652
Is Your Infrastructure Affected by CVE-2023-51652?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.