Server-side code execution via unescaped macro parameters
Published Apr 15, 2023 · Updated Feb 6, 2025
Eval injection in affected XWiki Platform releases allows remote authenticated users to execute arbitrary Groovy, Python, or Velocity code. ActivityMacro.xml inserts seven legacy activity-macro parameters into XWiki syntax without xwiki/2.1 escaping, allowing injected macro syntax to be evaluated. View rights on a commonly accessible document are sufficient, and successful execution grants full access to the XWiki installation.
Summary
What happened
Eval injection in affected XWiki Platform releases allows remote authenticated users to execute arbitrary Groovy, Python, or Velocity code. ActivityMacro.xml inserts seven legacy activity-macro parameters into XWiki syntax without xwiki/2.1 escaping, allowing injected macro syntax to be evaluated. View rights on a commonly accessible document are sufficient, and successful execution grants full access to the XWiki installation.
The record
- CVE
- CVE-2023-29209
- Published
- Apr 15, 2023
- Updated
- Feb 6, 2025
- Vendor
- CryptPad
- Product
- XWiki Platform
- Classifications
- CWE-94, CWE-95, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 10.9, < 13.10.11
- Affected versionversion=>= 14.0-rc-1, < 14.4.7
- Affected versionversion=>= 14.5, < 14.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream legacy activity macro proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo