# CVE-2023-26470: In XWiki Platform, saving a document with a large object number leads to persistent OOM errors > Attackers can cause persistent out-of-memory errors and service unavailability by adding objects with excessively large numbers to XWiki pages. - **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/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:** 2 Mar 2023 - **Updated:** 5 Mar 2025 - **Also known as:** GHSA-92wp-r7hm-42g7 ## What is CVE-2023-26470? CVE-2023-26470 is a medium-severity denial of service vulnerability in Xwiki Xwiki, published on 2 Mar 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. It's possible to make the farm unusable by adding an object to a page with a huge number (e.g. 67108863). Most of the time this will fill the memory allocated to XWiki and make it unusable every time this document is manipulated. This issue has been patched in XWiki 14.0-rc-1. Weakness: CWE-787 (Out-of-bounds Write), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2023-26470? 2 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-oldcore. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.xwiki.platform:xwiki-platform-oldcore` | Maven | All versions | 14.0-rc-1 | | `org.xwiki.platform:xwiki-platform-oldcore` | Maven | All versions | 14.0-rc-1 | Products: Xwiki Xwiki. ## How do I fix CVE-2023-26470? Upgrade org.xwiki.platform:xwiki-platform-oldcore to 14.0-rc-1 or later. ## Is CVE-2023-26470 being exploited? There is no known exploitation of CVE-2023-26470 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-2023-26470 and fix it if it is affected. What it is: CVE-2023-26470 is a medium-severity denial of service vulnerability in Xwiki Xwiki, published on 2 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2023-26470 in the wild and no public exploit code. Affected packages and fixed versions: - org.xwiki.platform:xwiki-platform-oldcore (Maven): affected all versions; fixed in 14.0-rc-1 - org.xwiki.platform:xwiki-platform-oldcore (Maven): affected all versions; fixed in 14.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-2023-26470/ (Markdown: https://insights.sbomify.com/CVE-2023-26470/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26470 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26470 - OSV: https://osv.dev/vulnerability/CVE-2023-26470 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-26470/ Summaries are generated and may contain mistakes; the official description above is the record.