Skip to content
Fencer Vulns
high 7.7

CVE-2021-21379 json

It's possible to execute anything with the rights of the author of a macro which uses the {{wikimacrocontent}} macro

published 2021-03-12 5 y ago modified 2026-07-08 4 mo ago also GHSA-v662-xpcc-9xf6 , EUVD-2021-0708

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

Summary

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. In affected versions of XWiki Platform, the `{{wikimacrocontent}}` executes the content with the rights of the wiki macro author instead of the caller of that wiki macro. This makes possible to inject scripts through it and they will be executed with the rights of the wiki macro (very often a user which has Programming rights). Fortunately, no such macro exists by default in XWiki Standard but one could have been created or installed with an extension. This vulnerability has been patched in versions XWiki 12.6.3, 11.10.11 and 12.8-rc-1. There is no easy workaround other than disabling the affected macros. Inserting content in a safe way or knowing what is the user who called the wiki macro is not easy.

Patch / fix

  • maven org.xwiki.platform:xwiki-platform-rendering-wikimacro-store 11.10.11, 12.6.3, 12.8
  • xwiki xwiki 11.10.11, 12.6.3

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.xwiki.platform:xwiki-platform-rendering-wikimacro-store
>=11.4, <11.10.11
>=12.0, <12.6.3
>=12.7, <12.8
11.10.11
12.6.3
12.8

Affected products

  • xwiki xwiki-platform

Classification

Weakness
  • CWE-281 Improper Preservation of Permissions

References

Sources

Fencer Vulns 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.