# CVE-2024-38369: XWiki programming rights may be inherited by inclusion > Attackers can execute code with the privileges of the user who included a document, allowing privilege escalation in XWiki. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Jun 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-qcj3-wpgm-qpxh ## What is CVE-2024-38369? CVE-2024-38369 is a critical vulnerability in Xwiki Xwiki, published on 24 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. The content of a document included using `{{include reference="targetdocument"/}}` is executed with the right of the includer and not with the right of its author. This means that any user able to modify the target document can impersonate the author of the content which used the `include` macro. This vulnerability has been patched in XWiki 15.0 RC1 by making the default behavior safe. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2024-38369? 2 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-rendering-macro-include. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.xwiki.platform:xwiki-platform-rendering-macro-include` | Maven | All versions | 15.0-rc-1 | | `org.xwiki.platform:xwiki-platform-rendering-macro-include` | Maven | All versions | 15.0-rc-1 | Products: Xwiki Xwiki. ## How do I fix CVE-2024-38369? Upgrade org.xwiki.platform:xwiki-platform-rendering-macro-include to 15.0-rc-1 or later. ## Is CVE-2024-38369 being exploited? There is no known exploitation of CVE-2024-38369 in the wild and no public exploit code. ## Other vulnerabilities in Xwiki Xwiki - [CVE-2025-24893](https://insights.sbomify.com/CVE-2025-24893/): XWiki Platform Eval Injection (critical 9.8, exploited in the wild) - [CVE-2025-53836](https://insights.sbomify.com/CVE-2025-53836/): XWiki Rendering is vulnerable to RCE attacks when processing nested macros (critical 10.0) - [CVE-2024-55662](https://insights.sbomify.com/CVE-2024-55662/): XWiki allows remote code execution through the extension sheet (critical 10.0) - [CVE-2024-55877](https://insights.sbomify.com/CVE-2024-55877/): XWiki allows remote code execution from account through macro descriptions and XWiki.XWikiSyntaxMacrosList (critical 10.0) - [CVE-2024-37901](https://insights.sbomify.com/CVE-2024-37901/): XWiki Platform vulnerable to remote code execution from account via SearchSuggestConfigSheet (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-38369 and fix it if it is affected. What it is: CVE-2024-38369 is a critical vulnerability in Xwiki Xwiki, published on 24 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-38369 in the wild and no public exploit code. Affected packages and fixed versions: - org.xwiki.platform:xwiki-platform-rendering-macro-include (Maven): affected all versions; fixed in 15.0-rc-1 - org.xwiki.platform:xwiki-platform-rendering-macro-include (Maven): affected all versions; fixed in 15.0-rc-1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-38369/ (Markdown: https://insights.sbomify.com/CVE-2024-38369/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38369 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38369 - OSV: https://osv.dev/vulnerability/CVE-2024-38369 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-38369/ Summaries are generated and may contain mistakes; the official description above is the record.