CVE-2025-53835

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2025-07-14. NVD baseline CVSS 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2025-21399 (ENISA EUVD) · GHSA-w3wh-g4m9-783p (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XWiki Rendering is a generic rendering system that converts textual input in a given syntax (wiki syntax, HTML, etc) into another syntax (XHTML, etc). Starting in version 5.4.5 and prior to version 14.10, the XHTML syntax depended on the xdom+xml/current syntax which allows the creation of raw blocks that permit the insertion of arbitrary HTML content including JavaScript. This allows XSS attacks for users who can edit a document like their user profile (enabled by default). This has been fixed in version 14.10 by removing the dependency on the xdom+xml/current syntax from the XHTML syntax. Note that the xdom+xml syntax is still vulnerable to this attack. As it's main purpose is testing and its use is quite difficult, this syntax shouldn't be installed or used on a regular wiki. There are no known workarounds apart from upgrading.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 14, 2025

Last Modified

August 26, 2025

Advisory Details (3)

Auto-updated Jul 25, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in a dependency of org.xwiki.rendering:xwiki-rendering-syntax-xhtml · Advisory · xwiki/xwiki-rendering · GitHub

https://github.com/xwiki/xwiki-rendering/security/advisories/GHSA-w3wh-g4m9-783p
Web page

Loading...

https://jira.xwiki.org/browse/XRENDERING-660
GitHub commit Patch Available

commit a4ca31f99f52 (xwiki/xwiki-rendering)

Patch available: xwiki/xwiki-rendering xwiki-rendering-17.4.8 (contains commit a4ca31f99f52)

https://github.com/xwiki/xwiki-rendering/commit/a4ca31f99f524b9456c64150d6f375984aa81ea7

Vendor Advisories for CVE-2025-53835(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.xwiki.rendering:xwiki-rendering-syntax-xhtml @ 14.10 (fixes >= 5.4.5, < 14.10)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.xwiki.rendering:xwiki-rendering-syntax-xhtml10.0 ... 9.9-rc-2 (321 versions)
  • 5.4.5 up to 14.10: fixed in 14.10
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 251 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 151 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-11-12 10:32 UTCEchelonGraph re-scored
  3. 2026-11-12 10:32 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  4. 2026-11-11 16:36 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-11-11 11:51 UTCEchelonGraph re-scored
  6. 2026-11-11 11:51 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  7. 2026-11-10 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-11-10 13:09 UTCEchelonGraph re-scored
  9. 2026-11-10 13:09 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  10. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-11-09 14:25 UTCEchelonGraph re-scored
  12. 2026-11-09 14:25 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  13. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-11-08 15:44 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  15. 2026-11-07 17:03 UTCEchelonGraph re-scored
  16. 2026-11-07 17:03 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  17. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-11-06 18:23 UTCEchelonGraph re-scored
  19. 2026-11-06 18:23 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  20. 2026-11-06 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-11-05 19:42 UTCEchelonGraph re-scored
  22. 2026-11-05 19:42 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  23. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-11-05 15:25 UTCOSV refresh
  25. 2026-11-04 21:02 UTCEchelonGraph re-scored
Show 73 more
  1. 2026-11-04 21:02 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  2. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-11-03 22:21 UTCEchelonGraph re-scored
  4. 2026-11-03 22:21 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  5. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-11-02 23:32 UTCEchelonGraph re-scored
  7. 2026-11-02 23:32 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  8. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-11-02 00:51 UTCEchelonGraph re-scored
  10. 2026-11-02 00:51 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  11. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-11-01 08:04 UTCGHSA enrichmentGHSA-w3wh-g4m9-783p · GitHub severity CRITICAL · GitHub CVSS 9.0
  13. 2026-11-01 08:04 UTCEchelonGraph re-scored
  14. 2026-11-01 02:11 UTCEchelonGraph re-scored
  15. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-31 03:30 UTCEchelonGraph re-scored
  17. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-30 04:48 UTCEchelonGraph re-scored
  19. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-29 06:07 UTCEchelonGraph re-scored
  21. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-28 07:27 UTCEchelonGraph re-scored
  23. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-10-27 08:46 UTCEchelonGraph re-scored
  25. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-10-26 08:14 UTCEchelonGraph re-scored
  27. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-10-25 16:19 UTCEchelonGraph re-scored
  29. 2026-10-25 09:32 UTCEchelonGraph re-scored
  30. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  31. 2026-10-24 10:51 UTCEchelonGraph re-scored
  32. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-10-23 12:10 UTCEchelonGraph re-scored
  34. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  35. 2026-10-22 13:24 UTCEchelonGraph re-scored
  36. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  37. 2026-10-21 14:38 UTCEchelonGraph re-scored
  38. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  39. 2026-10-20 15:13 UTCEchelonGraph re-scored
  40. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  41. 2026-10-18 16:48 UTCEchelonGraph re-scored
  42. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-10-18 05:26 UTCEchelonGraph re-scored
  44. 2026-10-17 18:07 UTCEchelonGraph re-scored
  45. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-10-16 19:24 UTCEchelonGraph re-scored
  47. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  48. 2026-10-15 16:59 UTCEchelonGraph re-scored
  49. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  50. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  51. 2026-10-14 11:00 UTCEchelonGraph re-scored
  52. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  53. 2026-10-12 16:57 UTCEchelonGraph re-scored
  54. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  55. 2026-10-11 20:31 UTCEchelonGraph re-scored
  56. 2026-10-11 18:42 UTCEchelonGraph re-scored
  57. 2026-10-11 15:18 UTCEchelonGraph re-scored
  58. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  59. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  60. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  61. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  62. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  63. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  64. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  65. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  66. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  67. 2026-10-02 09:40 UTCOSV refresh
  68. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  69. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  70. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  71. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  72. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  73. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 26th percentile

Related CVEs(same product + same CWE)

Same product

1 shown

Maven:org.xwiki.rendering:xwiki-rendering-syntax-xhtml

Frequently asked(5)

What is CVE-2025-53835?
CVE-2025-53835 is a critical-severity vulnerability; its CVE record was published on July 14, 2025. XWiki Rendering is a generic rendering system that converts textual input in a given syntax (wiki syntax, HTML, etc) into another syntax (XHTML, etc). Starting in version 5.4.5 and prior to version 14.10, the XHTML syntax depended on the xdom+xml/current syntax which allows the creation of raw…
When was the CVE record for CVE-2025-53835 published?
The CVE record for CVE-2025-53835 was published on July 14, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 26, 2025; the record at its source may have been updated since.
Is CVE-2025-53835 actively exploited?
CVE-2025-53835 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-53835?
CVE-2025-53835 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2025-53835?
A fix for CVE-2025-53835 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-53835 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-53835

Explore →

Is Your Infrastructure Affected by CVE-2025-53835?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs