Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-9j36-3cp4-rh4j

CRITICAL

GHSA-9j36-3cp4-rh4j is a critical-severity (CVSS 9.9) CWE-74 vulnerability in org.xwiki.platform.applications:xwiki-application-administration. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-9j36-3cp4-rh4j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XWiki vulnerable to Code Injection in template provider administration

Also known asCVE-2023-29514
Published
Apr 20, 2023
Updated
Nov 8, 2023
Affected
5 pkgs
Patched
3 / 5
Exploits
2 known

Blast Radius

5 pkgs affected
org.xwiki.platform.applications:xwiki-application-administrationorg.xwiki.platform:xwiki-platform-administrationorg.xwiki.platform:xwiki-platform-administration-uiorg.xwiki.platform:xwiki-platform-administration-uiorg.xwiki.platform:xwiki-platform-administration-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

Any user with edit rights on any document (e.g., the own user profile) can execute code with programming rights, leading to remote code execution by following these steps:

  1. Set the title of any document you can edit (can be the user profile) to
    {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("Hello " + "from groovy!"){{/groovy}}{{/async}}
  1. Use the object editor to add an object of type XWiki.TemplateProviderClass (named "Template Provider Class") to that document.
  2. Go to another document you can view (can be the home page) and append ?sheet=XWiki.AdminTemplatesSheet to the URL.

When the attack is successful, a template with name "Hello from groovy!" is displayed in the list while on fixed systems, the full title should be displayed.

Patches

This vulnerability has been patched in XWiki 13.10.11, 14.4.8, 14.10.1 and 15.0 RC1.

Workarounds

The vulnerability can be fixed by patching the code in the affected XWiki document as shown in the patch.

References

For more information

If you have any questions or comments about this advisory:

Affected Packages

5 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform.applications:xwiki-application-administration1.35No fix
Mavenorg.xwiki.platform:xwiki-platform-administration3.1-milestone-1No fix
Mavenorg.xwiki.platform:xwiki-platform-administration-ui4.2-milestone-1&&< 13.10.1113.10.11
Mavenorg.xwiki.platform:xwiki-platform-administration-ui14.0-rc-1&&< 14.4.814.4.8
Mavenorg.xwiki.platform:xwiki-platform-administration-ui14.5&&< 14.10.114.10.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.applications:xwiki-application-administration. 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.

  2. Fix

    No patched version of org.xwiki.platform.applications:xwiki-application-administration has shipped for GHSA-9j36-3cp4-rh4j yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  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 pinpoints whether GHSA-9j36-3cp4-rh4j 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 GHSA-9j36-3cp4-rh4j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Any user with edit rights on any document (e.g., the own user profile) can execute code with programming rights, leading to remote code execution by following these steps: 1. Set the title of any document you can edit (can be the user profile) to ``` {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("Hello " + "from groovy!"){{/groovy}}{{/async}} ``` 2. Use the object editor to add an object of type `XWiki.TemplateProviderClass` (named "Template Provider Class") to that document. 3. Go to another document you can view (can be the home page) and app
O3 Security · Impact-Aware SCA

Is GHSA-9j36-3cp4-rh4j in your dependencies?

O3 detects GHSA-9j36-3cp4-rh4j across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.