CVE-2023-26479: org.xwiki.platform:xwiki-platform-rendering-parser vulnerable to Improper Handling of Exceptional Conditions
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.xwiki.platform:xwiki-platform-rendering-parser (Maven) 14.4.6, 14.9-rc-1, 13.10.10.
Low priority for now. Upgrade to org.xwiki.platform:xwiki-platform-rendering-parser (Maven) 14.4.6, 14.9-rc-1, 13.10.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 2, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-755
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · GitHub_M
- 6.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xwiki | xwiki | cpe:2.3:a:xwiki:xwiki |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
xwiki xwiki-platform
- >= 6.0, < 13.10.10, >= 14.0, < 14.4.6, >= 14.5, < 14.9-rc-1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xwiki xwiki6.0 and later · before 13.10.10
- xwiki xwiki14.0 and later · before 14.4.6
- xwiki xwiki14.5 and later · before 14.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.xwiki.platform:xwiki-platform-rendering-parser | from 14.0 · before 14.4.6 | 14.4.6 |
| Maven | org.xwiki.platform:xwiki-platform-rendering-parser | from 14.5 · before 14.9-rc-1 | 14.9-rc-1 |
| Maven | org.xwiki.platform:xwiki-platform-rendering-parser | from 6.0 · before 13.10.10 | 13.10.10 |
Same product
xwiki: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-24893Remote code execution as guest via SolrSearchMacros request in xwikiKEV99Now
- CVE-2024-21650XWiki Remote Code Execution vulnerability via user registration67This week
- CVE-2023-46731Remote code execution through the section parameter in Administration as guest in XWiki Platform66This week
Published before and after this one in the same product
- ← EarlierCVE-2023-26477Mar 2, 2023 · org.xwiki.platform:xwiki-platform-flamingo-theme-ui Eval Injection vulnerability61This week
- ← EarlierCVE-2023-26478Mar 2, 2023 · org.xwiki.platform:xwiki-platform-store-filesystem-oldcore has Exposed Dangerous Method or Function32Monitor
- Later →CVE-2023-26480Mar 2, 2023 · XWiki-Platform vulnerable to stored Cross-site Scripting via the HTML displayer in Live Data21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.xwiki.platform:xwiki-platform-rendering-parser | 13.10.10 | Package registry (OSV) |
| Maven:org.xwiki.platform:xwiki-platform-rendering-parser | 14.4.6 | Package registry (OSV) |
| Maven:org.xwiki.platform:xwiki-platform-rendering-parser | 14.9-rc-1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-755 · Improper Handling of Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.