How severe is CVE-2023-36470?

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

Which packages are affected by CVE-2023-36470?

CVE-2023-36470 affects the following packages: org.xwiki.platform:xwiki-platform-icon-default (Maven), org.xwiki.platform:xwiki-platform-icon-script (Maven), org.xwiki.platform:xwiki-platform-icon-script (Maven), org.xwiki.platform:xwiki-platform-icon-default (Maven), org.xwiki.platform:xwiki-platform-icon-ui (Maven), org.xwiki.platform:xwiki-platform-icon-ui (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-36470?

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

How do I detect CVE-2023-36470 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-icon-default. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2023-36470?

O3 pinpoints whether CVE-2023-36470 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Yes. There are 2 known exploit references for CVE-2023-36470, 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-36470?

CVE-2023-36470 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 74th 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.

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

CVE-2023-36470 was published on June 29, 2023 and was last updated on April 10, 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

CVE-2023-36470

CRITICAL

Code injection in icon themes of XWiki Platform

Also known asGHSA-fm68-j7ww-h9xf

Published

Jun 29, 2023

Updated

Apr 10, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk74th percentile-10.94%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

☕org.xwiki.platform:xwiki-platform-icon-default☕org.xwiki.platform:xwiki-platform-icon-script☕org.xwiki.platform:xwiki-platform-icon-script☕org.xwiki.platform:xwiki-platform-icon-default☕org.xwiki.platform:xwiki-platform-icon-ui☕org.xwiki.platform:xwiki-platform-icon-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

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. By either creating a new or editing an existing document with an icon set, an attacker can inject XWiki syntax and Velocity code that is executed with programming rights and thus allows remote code execution. There are different attack vectors, the simplest is the Velocity code in the icon set's HTML or XWiki syntax definition. The icon picker can be used to trigger the rendering of any icon set. The XWiki syntax variant of the icon set is also used without any escaping in some documents, allowing to inject XWiki syntax including script macros into a document that might have programming right, for this the currently used icon theme needs to be edited. Further, the HTML output of the icon set is output as JSON in the icon picker and this JSON is interpreted as XWiki syntax, allowing again the injection of script macros into a document with programming right and thus allowing remote code execution. This impacts the confidentiality, integrity and availability of the whole XWiki instance. This issue has been patched in XWiki 14.10.6 and 15.1. Icon themes now require script right and the code in the icon theme is executed within the context of the icon theme, preventing any rights escalation. A macro for displaying icons has been introduced to avoid injecting the raw wiki syntax of an icon set into another document. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-icon-default`	≥ 6.2-milestone-1&&< 14.10.6	14.10.6
☕Maven	`org.xwiki.platform:xwiki-platform-icon-script`	≥ 6.2-milestone-1&&< 14.10.6	14.10.6
☕Maven	`org.xwiki.platform:xwiki-platform-icon-script`	≥ 15.0-rc-1&&< 15.2-rc-1	15.2-rc-1
☕Maven	`org.xwiki.platform:xwiki-platform-icon-default`	≥ 15.0-rc-1&&< 15.2-rc-1	15.2-rc-1
☕Maven	`org.xwiki.platform:xwiki-platform-icon-ui`	≥ 6.2-milestone-1&&< 14.10.6	14.10.6
☕Maven	`org.xwiki.platform:xwiki-platform-icon-ui`	≥ 15.0-rc-1&&< 15.2-rc-1	15.2-rc-1

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 …

github.comNVDJul 2023

XWiki Platform is a generic wiki platform offering runtime services for …

jira.xwiki.orgNVDJul 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-icon-default. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.xwiki.platform:xwiki-platform-icon-default to 14.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-36470 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2023-36470 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-36470. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-36470 in your dependencies?

O3 detects CVE-2023-36470 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works