CVE-2022-36100

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2022-09-16. NVD baseline CVSS 9.9; sources differ by 0.0.

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

Also known asEUVD-2022-6660 (ENISA EUVD) · GHSA-2g5c-228j-p52x (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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).
  • High exploitation likelihood — EPSS 74%
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 74%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

XWiki Platform Applications Tag and XWiki Platform Tag UI are tag applications for XWiki, a generic wiki platform. Starting with version 1.7 in XWiki Platform Applications Tag and prior to 13.10.6 and 14.4 in XWiki Platform Tag UI, the tags document Main.Tags in XWiki didn't sanitize user inputs properly. This allowed users with view rights on the document (default in a public wiki or for authenticated users on private wikis) to execute arbitrary Groovy, Python and Velocity code with programming rights. This also allowed bypassing all rights checks and thus both modification and disclosure of all content stored in the XWiki installation. The vulnerability could be used to impact the availability of the wiki. On XWiki versions before 13.10.4 and 14.2, this can be combined with CVE-2022-36092, meaning that no rights are required to perform the attack. The vulnerability has been patched in versions 13.10.6 and 14.4. As a workaround, the patch that fixes the issue can be manually applied to the document Main.Tags or the updated version of that document can be imported from version 14.4 of xwiki-platform-tag-ui using the import feature in the administration UI on XWiki 10.9 and later.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
74
EG Risk 74/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation74% × 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 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
74%
EPSS %ILE
99th
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
74% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

September 8, 2022

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit.
Web page

Loading...

https://jira.xwiki.org/browse/XWIKI-19747
GitHub advisoryMentions a patch (unverified)

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in xwiki-platform-tag-ui · Advisory · xwiki/xwiki-platform · GitHub

https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-2g5c-228j-p52x
GitHub commit Patch Available

commit 604868033ebd (xwiki/xwiki-platform)

Patch available: xwiki/xwiki-platform xwiki-platform-18.3.0 (contains commit 604868033ebd)

https://github.com/xwiki/xwiki-platform/commit/604868033ebd191cf2d1e94db336f0c4d9096427

Vendor Advisories for CVE-2022-36100(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.xwiki.platform.applications:xwiki-application-tag—ghsa
mavenorg.xwiki.platform:xwiki-platform-tag-ui @ 13.10.6 (fixes < 13.10.6)—ghsa
mavenorg.xwiki.platform:xwiki-platform-tag-ui @ 14.4 (fixes >= 14.0, < 14.4)—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

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.xwiki.platform.applications:xwiki-application-tag—
  • 1.7 on: no fix on record
—
org.xwiki.platform:xwiki-platform-tag-ui—
  • every version up to 13.10.6: fixed in 13.10.6
  • 14.0 up to 14.4: fixed in 14.4
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 31× 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 199 rows on record for this CVE, as 99 entries (1 repeat 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Maven:org.xwiki.platform:xwiki-platform-tag-ui

Frequently asked(5)

What is CVE-2022-36100?
CVE-2022-36100 is a critical-severity vulnerability; its CVE record was published on September 8, 2022. XWiki Platform Applications Tag and XWiki Platform Tag UI are tag applications for XWiki, a generic wiki platform. Starting with version 1.7 in XWiki Platform Applications Tag and prior to 13.10.6 and 14.4 in XWiki Platform Tag UI, the tags document Main.Tags in XWiki didn't sanitize user inputs…
When was the CVE record for CVE-2022-36100 published?
The CVE record for CVE-2022-36100 was published on September 8, 2022. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-36100 actively exploited?
CVE-2022-36100 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 74% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-36100?
CVE-2022-36100 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2022-36100?
A fix for CVE-2022-36100 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-36100 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-2022-36100

Explore →

Is Your Infrastructure Affected by CVE-2022-36100?

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

Book a Demo →Browse All CVEs