Skip to content
Fencer Intel
critical 9.9

CVE-2022-36100 in the critical feed json

XWiki Platform Applications Tag and XWiki Platform Tag UI vulnerable to Eval Injection

published 4y ago modified 4mo ago also GHSA-2g5c-228j-p52x , EUVD-2022-6660

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
73.6%
EPSS 73.6% chance of exploitation in 30 days, percentile 99.4%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.xwiki.platform:xwiki-platform-tag-ui 13.10.6, 14.4
  • xwiki xwiki 13.10.6, 14.4

Is CVE-2022-36100 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

73.61% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-2g5c-228j-p52x referenced PoC, tagged "exploit" by a source, unverified
  • jira.xwiki.org https://jira.xwiki.org/browse/XWIKI-19747 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.xwiki.platform:xwiki-platform-tag-ui
<13.10.6
>=14.0, <14.4
13.10.6
14.4
maven org.xwiki.platform.applications:xwiki-application-tag
>=1.7
 no fix listed

Affected products

  • xwiki xwiki-platform

Classification

Weakness
  • CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code
  • CWE-94 Improper Control of Generation of Code
  • CWE-116 Improper Encoding or Escaping of Output

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.