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

CVE-2026-44179 — xwiki-pro-macros

CRITICAL

CVE-2026-44179 is a critical-severity (CVSS 9.9) remote code execution vulnerability in com.xwiki.pro:xwiki-pro-macros. A fix is available for com.xwiki.pro:xwiki-pro-macros — see the affected versions and patch details below.

xwiki-pro-macros has remote code execution from page title and content via excerpt-include macro

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jun 22, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
☕com.xwiki.pro:xwiki-pro-macros

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

Summary

The excerpt-include macro does not properly escape the title of the included page and executes the content of the excerpt with the macro's rights. Therefore, it is vulnerable to XWiki syntax injection via the included page's title and content, allowing remote code execution for any user who can edit a page.

Details

The title of the included page isn't escaped in ExcerptInclude.xml#L277. Further, the content of the excerpt macro is rendered to XWiki syntax and output into the macro's content such that it is executed with the macro's rights.

PoC

  1. As a user without script or programming right, create a page named Exploit.
  2. In the edit screen, change the title to {{async}}{{groovy}}println("Hello from Groovy Title!"){{/groovy}}{{/async}}.
  3. Set the content to
{{excerpt-include 0="Exploit.WebHome"}}{{/excerpt-include}}

{{excerpt}}
  {{async}}{{groovy}}println("Hello from Groovy content!"){{/groovy}}{{/async}}
{{/excerpt}}
  1. Save and view the page.
  2. If this displays "Hello from Groovy Title!" without the surrounding macro code or "Hello from Groovy content!", the attack succeeded.

Impact

Remote code execution impacts the confidentiality, integrity and availability of the whole XWiki installation.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.xwiki.pro:xwiki-pro-macros≥ 1.13&&< 1.14.51.14.5com.xwiki.pro:xwiki-pro-macros:1.14.5

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update com.xwiki.pro:xwiki-pro-macros to 1.14.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44179 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.

Frequently Asked Questions

### Summary The excerpt-include macro does not properly escape the title of the included page and executes the content of the excerpt with the macro's rights. Therefore, it is vulnerable to XWiki syntax injection via the included page's title and content, allowing remote code execution for any user who can edit a page. ### Details The title of the included page isn't escaped in [ExcerptInclude.xml#L277](https://github.com/xwikisas/xwiki-pro-macros/blob/main/xwiki-pro-macros-ui/src/main/resources/Confluence/Macros/ExcerptInclude.xml#L277). Further, the content of the excerpt macro is rendered
O3 Security · Impact-Aware SCA

Is CVE-2026-44179 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-44179: xwiki-pro-macros RCE — Fixed in 1.14.5