How severe is CVE-2023-26471?

CVE-2023-26471 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-26471?

CVE-2023-26471 affects the following packages: org.xwiki.platform:xwiki-platform-rendering-async-macro (Maven), org.xwiki.platform:xwiki-platform-rendering-async-macro (Maven), org.xwiki.platform:xwiki-platform-rendering-async-macro (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-26471?

Update org.xwiki.platform:xwiki-platform-rendering-async-macro to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26471 is resolved across your whole dependency graph.

How do I detect CVE-2023-26471 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-rendering-async-macro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-26471 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2023-26471 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-26471, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-26471?

CVE-2023-26471 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-26471?

CVE-2023-26471 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-26471 published, and has it been updated?

CVE-2023-26471 was published on March 2, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2023-26471 — xwiki-platform-rendering-…

CRITICALFix: xwiki/xwiki-platform@00532d9

CVE-2023-26471 is a critical-severity (CVSS 9.9) CWE-284 vulnerability in org.xwiki.platform:xwiki-platform-rendering-async-macro. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-rendering-async-macro — see the affected versions and patch details below.

XWiki Platform users may execute anything with superadmin right through comments and async macro

Also known asGHSA-9cqm-5wf7-wcj7

Published

Mar 2, 2023

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-26471.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-rendering-async-macro☕org.xwiki.platform:xwiki-platform-rendering-async-macro☕org.xwiki.platform:xwiki-platform-rendering-async-macro

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Comments are supposed to be executed with the right of superadmin but in restricted mode (anything dangerous is disabled) but the async macro is not taking into account the restricted mode.

This means that any user with comment right can use the async macro to make it execute any wiki content with the right of superadmin as in:

{{async}} {{groovy}}println "it works !"{{/groovy}} {{/async}}

Patches

This has been patched in XWiki 14.9, 14.4.6, and 13.10.10.

Workarounds

The only known workaround consists in applying the following patch and rebuilding and redeploying org.xwiki.platform:xwiki-platform-rendering-async-macro.

References

https://jira.xwiki.org/browse/XWIKI-20234

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira
Email us at Security ML

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-rendering-async-macro`	≥ 11.6-rc-1&&< 13.10.10	13.10.10`org.xwiki.platform:xwiki-platform-rendering-async-macro:13.10.10`
☕Maven	`org.xwiki.platform:xwiki-platform-rendering-async-macro`	≥ 14.0&&< 14.4.6	14.4.6`org.xwiki.platform:xwiki-platform-rendering-async-macro:14.4.6`
☕Maven	`org.xwiki.platform:xwiki-platform-rendering-async-macro`	≥ 14.5&&< 14.9	14.9`org.xwiki.platform:xwiki-platform-rendering-async-macro:14.9`

Affected Products

1 product · 4 configurations

Application

xwikixwiki

≥ 14.5 && < 14.9

1 version

11.6

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

XWiki Platform is a generic wiki platform. Starting in version 11.6-rc-1…

jira.xwiki.orgNVDMar 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-rendering-async-macro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-rendering-async-macro to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26471 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact Comments are supposed to be executed with the right of superadmin but in restricted mode (anything dangerous is disabled) but the async macro is not taking into account the restricted mode. This means that any user with comment right can use the async macro to make it execute any wiki content with the right of superadmin as in: {{async}} {{groovy}}println "it works !"{{/groovy}} {{/async}} ### Patches This has been patched in XWiki 14.9, 14.4.6, and 13.10.10. ### Workarounds The only known workaround consists in applying [the following patch](https://github.com/xwiki/xwiki-pl