# CVE-2023-45135: XWiki users can be tricked to execute scripts as the create page action doesn't display the page's title > Attackers can trick users into executing malicious scripts via hidden page titles, leading to code execution or full instance compromise. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something - **Fix available:** Yes - **Published:** 25 Oct 2023 - **Updated:** 10 Sep 2024 - **Also known as:** GHSA-ghf6-2f42-mjh9 ## What is CVE-2023-45135? CVE-2023-45135 is a critical code injection vulnerability in Xwiki Xwiki, published on 25 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. In `org.xwiki.platform:xwiki-platform-web` versions 7.2-milestone-2 until 14.10.12 and `org.xwiki.platform:xwiki-platform-web-templates` prior to versions 14.10.12 and 15.5-rc-1, it is possible to pass a title to the page creation action that isn't displayed at first but then executed in the second step. This can be used by an attacker to trick a victim to execute code, allowing script execution if the victim has script right or remote code execution including full access to the XWiki instance if the victim has programming right. For the attack to work, the attacker needs to convince the victim to visit a link like `/xwiki/bin/create/NonExistingSpace/WebHome?title=$services.logging.getLogger(%22foo%22).error(%22Script%20executed!%22)` where `` is the URL of the Wiki installation and to then click on the "Create" button on that page. The page looks like a regular XWiki page that the victim would also see when clicking the button to create a page that doesn't exist yet, the malicious code is not displayed anywhere on that page. After clicking the "Create" button, the malicious title would be displayed but at this point, the code has already been executed and the attacker could use this code also to hide the attack, e.g., by redirecting the victim again to the same page with an innocent title. It thus seems plausible that this attack could work if the attacker can place a fake "create page" button on a page which is possible with edit right. This has been patched in `org.xwiki.platform:xwiki-platform-web` version 14.10.12 and `org.xwiki.platform:xwiki-platform-web-templates` versions 14.10.12 and 15.5-rc-1 by displaying the title already in the first step such that the victim can notice the attack before continuing. It is possible to manually patch the modified files from the patch in an existing installation. For the JavaScript change, the minified JavaScript file would need to be obtained from a build of XWiki and replaced accordingly. Weakness: CWE-116 (Improper Encoding or Escaping of Output) ## Which versions are affected by CVE-2023-45135? 6 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-web-templates and org.xwiki.platform:xwiki-platform-web. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.xwiki.platform:xwiki-platform-web-templates` | Maven | All versions | 14.10.12 | | `org.xwiki.platform:xwiki-platform-web-templates` | Maven | All versions | 14.10.12 | | `org.xwiki.platform:xwiki-platform-web-templates` | Maven | From 15.0-rc-1 | 15.5-rc-1 | | `org.xwiki.platform:xwiki-platform-web-templates` | Maven | From 15.0-rc-1 | 15.5-rc-1 | | `org.xwiki.platform:xwiki-platform-web` | Maven | From 7.2-milestone-2 | 14.10.12 | | `org.xwiki.platform:xwiki-platform-web` | Maven | From 7.2-milestone-2 | 14.10.12 | Products: Xwiki Xwiki. ## How do I fix CVE-2023-45135? Upgrade org.xwiki.platform:xwiki-platform-web-templates to a fixed version for your release line: 14.10.12 or 15.5-rc-1. ## Is CVE-2023-45135 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45135 exists. ## 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-2023-45135 and fix it if it is affected. What it is: CVE-2023-45135 is a critical code injection vulnerability in Xwiki Xwiki, published on 25 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45135 exists. Affected packages and fixed versions: - org.xwiki.platform:xwiki-platform-web-templates (Maven): affected all versions; fixed in 14.10.12 - org.xwiki.platform:xwiki-platform-web-templates (Maven): affected all versions; fixed in 14.10.12 - org.xwiki.platform:xwiki-platform-web-templates (Maven): affected from 15.0-rc-1; fixed in 15.5-rc-1 - org.xwiki.platform:xwiki-platform-web-templates (Maven): affected from 15.0-rc-1; fixed in 15.5-rc-1 - org.xwiki.platform:xwiki-platform-web (Maven): affected from 7.2-milestone-2; fixed in 14.10.12 - org.xwiki.platform:xwiki-platform-web (Maven): affected from 7.2-milestone-2; fixed in 14.10.12 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-2023-45135/ (Markdown: https://insights.sbomify.com/CVE-2023-45135/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45135 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45135 - OSV: https://osv.dev/vulnerability/CVE-2023-45135 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-45135/ Summaries are generated and may contain mistakes; the official description above is the record.