How severe is CVE-2023-29213?

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

Which packages are affected by CVE-2023-29213?

CVE-2023-29213 affects the following packages: org.xwiki.platform:xwiki-platform-logging-ui (Maven), org.xwiki.platform:xwiki-platform-logging-ui (Maven), org.xwiki.platform:xwiki-platform-logging-ui (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-29213?

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

How do I detect CVE-2023-29213 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-logging-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

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

Yes. There are 2 known exploit references for CVE-2023-29213, including 2 in-the-wild exploitations 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-29213?

CVE-2023-29213 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th 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-29213?

CVE-2023-29213 is classified as CWE-74 (CWE-74), Cross-Site Request Forgery (CSRF) (CWE-352). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2023-29213 was published on April 17, 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-29213 — xwiki-platform-logging-ui

CRITICALFix: xwiki/xwiki-platform@49fdfd6

CVE-2023-29213 is a critical-severity (CVSS 9) CWE-74 vulnerability in org.xwiki.platform:xwiki-platform-logging-ui. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-logging-ui — see the affected versions and patch details below.

org.xwiki.platform:xwiki-platform-logging-ui Injection vulnerability

Also known asGHSA-4655-wh7v-3vmg

Published

Apr 17, 2023

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

Exploitation data as of Nov 1, 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-29213.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% 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-logging-ui☕org.xwiki.platform:xwiki-platform-logging-ui☕org.xwiki.platform:xwiki-platform-logging-ui

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

Steps to reproduce:

It is possible to trick a user with programming rights into visiting <xwiki-host>/xwiki/bin/view/XWiki/LoggingAdmin?loggeraction_set=1&logger_name=%7B%7Bcache%7D%7D%7B%7Bgroovy%7D%7Dnew+File%28%22%2Ftmp%2Fexploit.txt%22%29.withWriter+%7B+out+-%3E+out.println%28%22created+from+notification+filter+preferences%21%22%29%3B+%7D%7B%7B%2Fgroovy%7D%7D%7B%7B%2Fcache%7D%7D&logger_level=TRACE where <xwiki-host> is the URL of your XWiki installation, e.g., by embedding an image with this URL in a document that is viewed by a user with programming rights.

Expected result:

No file in /tmp/exploit.txt has been created.

Actual result:

The file /tmp/exploit.txt is been created with content "created from notification filter preferences!". This demonstrates a CSRF remote code execution vulnerability that could also be used for privilege escalation or data leaks (if the XWiki installation can reach remote hosts).

Patches

The problem has been patched on XWiki 14.4.7, and 14.10.

Workarounds

The issue can be fixed manually applying this patch.

References

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki.org
Email us at Security Mailing List

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-logging-ui`	≥ 4.2-milestone-3&&< 13.10.11	13.10.11`org.xwiki.platform:xwiki-platform-logging-ui:13.10.11`
☕Maven	`org.xwiki.platform:xwiki-platform-logging-ui`	≥ 14.0-rc-1&&< 14.4.7	14.4.7`org.xwiki.platform:xwiki-platform-logging-ui:14.4.7`
☕Maven	`org.xwiki.platform:xwiki-platform-logging-ui`	≥ 14.5&&< 14.10	14.10`org.xwiki.platform:xwiki-platform-logging-ui:14.10`

Affected Products

1 product · 7 configurations

Application

xwikixwiki

≥ 14.5 && < 14.10

2 versions

4.214.0

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 offering runtime services for …

jira.xwiki.orgNVDMay 2023

Report on github.com

github.comNVDMay 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-logging-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-logging-ui to 13.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-29213 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### Impact #### Steps to reproduce: It is possible to trick a user with programming rights into visiting <xwiki-host>/xwiki/bin/view/XWiki/LoggingAdmin?loggeraction_set=1&logger_name=%7B%7Bcache%7D%7D%7B%7Bgroovy%7D%7Dnew+File%28%22%2Ftmp%2Fexploit.txt%22%29.withWriter+%7B+out+-%3E+out.println%28%22created+from+notification+filter+preferences%21%22%29%3B+%7D%7B%7B%2Fgroovy%7D%7D%7B%7B%2Fcache%7D%7D&logger_level=TRACE where <xwiki-host> is the URL of your XWiki installation, e.g., by embedding an image with this URL in a document that is viewed by a user with programming rights. #### Expect