Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

GHSA-fm68-j7ww-h9xf — xwiki-platform-icon-defau…

CRITICALFix: xwiki/xwiki-platform@46b5428

GHSA-fm68-j7ww-h9xf is a critical-severity (CVSS 9.9) CWE-74 vulnerability in org.xwiki.platform:xwiki-platform-icon-default. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-icon-default — see the affected versions and patch details below.

XWiki Platform vulnerable to Code Injection in icon themes

Also known asCVE-2023-36470
Published
Jun 30, 2023
Updated
Nov 8, 2023
Affected
6 pkgs
Patched
6 / 6
Exploits
2 known
Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fm68-j7ww-h9xf.

EPSS Exploitation Probability

via FIRST.org ↗
1.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

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.

How urgent is this, really

GHSA-fm68-j7ww-h9xf plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

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

Impact

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.

Patches

This 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.

Workarounds

There are no workarounds apart from upgrading to a version containing the fix.

References

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.xwiki.platform:xwiki-platform-icon-default≥ 6.2-milestone-1&&< 14.10.614.10.6org.xwiki.platform:xwiki-platform-icon-default:14.10.6
☕Mavenorg.xwiki.platform:xwiki-platform-icon-script≥ 6.2-milestone-1&&< 14.10.614.10.6org.xwiki.platform:xwiki-platform-icon-script:14.10.6
☕Mavenorg.xwiki.platform:xwiki-platform-icon-script≥ 15.0-rc-1&&< 15.2-rc-115.2-rc-1org.xwiki.platform:xwiki-platform-icon-script:15.2-rc-1
☕Mavenorg.xwiki.platform:xwiki-platform-icon-default≥ 15.0-rc-1&&< 15.2-rc-115.2-rc-1org.xwiki.platform:xwiki-platform-icon-default:15.2-rc-1
☕Mavenorg.xwiki.platform:xwiki-platform-icon-ui≥ 6.2-milestone-1&&< 14.10.614.10.6org.xwiki.platform:xwiki-platform-icon-ui:14.10.6
☕Mavenorg.xwiki.platform:xwiki-platform-icon-ui≥ 15.0-rc-1&&< 15.2-rc-115.2-rc-1org.xwiki.platform:xwiki-platform-icon-ui:15.2-rc-1
Exploits & PoCs
2

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. 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 GHSA-fm68-j7ww-h9xf is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fm68-j7ww-h9xf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-fm68-j7ww-h9xf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact 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](https://extensions.xwiki.org/xwiki/bin/view/Extension/Icon%20Theme%20Application#HIconPicker) 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,
O3 Security · Impact-Aware SCA

Is GHSA-fm68-j7ww-h9xf in your dependencies?

O3 Security finds GHSA-fm68-j7ww-h9xf across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-fm68-j7ww-h9xf: RCE (Critical 9.9) | O3 Security