CVE-2023-37908: org.xwiki.rendering:xwiki-rendering-xml Improper Neutralization of Invalid Characters in Identifiers in Web Pages vulnerability
Noroxi assessment
Priority: Monitor (action score 38/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: org.xwiki.platform:xwiki-platform-annotation-core (Maven) 14.6-rc-1; org.xwiki.rendering:xwiki-rendering-syntax-annotatedhtml5 (Maven) 14.6-rc-1; org.xwiki.rendering:xwiki-rendering-syntax-annotatedxhtml (Maven) 14.6-rc-1.
Low priority for now. Upgrade to org.xwiki.platform:xwiki-platform-annotation-core (Maven) 14.6-rc-1; org.xwiki.rendering:xwiki-rendering-syntax-annotatedhtml5 (Maven) 14.6-rc-1; org.xwiki.rendering:xwiki-rendering-syntax-annotatedxhtml (Maven) 14.6-rc-1 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 Rendering is a generic Rendering system that converts textual input in a given syntax into another syntax. The cleaning of attributes during XHTML rendering, introduced in version 14.6-rc-1, allowed the injection of arbitrary HTML code and thus cross-site scripting via invalid attribute names. This can be exploited, e.g., via the link syntax in any content that supports XWiki syntax like comments in XWiki. When a user moves the mouse over a malicious link, the malicious JavaScript code is executed in the context of the user session. When this user is a privileged user who has programming rights, this allows server-side code execution with programming rights, impacting the confidentiality, integrity and availability of the XWiki instance. While this attribute was correctly recognized as not allowed, the attribute was still printed with a prefix `data-xwiki-translated-attribute-` without further cleaning or validation. This problem has been patched in XWiki 14.10.4 and 15.0 RC1 by removing characters not allowed in data attributes and then validating the cleaned attribute again. There are no known workarounds apart from upgrading to a version including the fix.
- Published
- Oct 25, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-83
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 38 / 40 · 9.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.6
- CNA · GitHub_M
- 9.1
- 0.5 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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-rendering | cpe:2.3:a:xwiki:xwiki-rendering |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xwiki xwiki-rendering14.6 and later · before 14.10.4
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-rendering
- >= 14.6-rc-1, < 14.10.4affected
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-core-rendering-api | up to and including 3.0-milestone-2 | — |
| Maven | org.xwiki.platform:xwiki-platform-annotation-core | before 14.6-rc-1 | 14.6-rc-1 |
| Maven | org.xwiki.rendering:xwiki-rendering-syntax-annotatedhtml5 | before 14.6-rc-1 | 14.6-rc-1 |
| Maven | org.xwiki.rendering:xwiki-rendering-syntax-annotatedxhtml | before 14.6-rc-1 | 14.6-rc-1 |
| Maven | org.xwiki.rendering:xwiki-rendering-syntax-html | before 14.6-rc-1 | 14.6-rc-1 |
| Maven | org.xwiki.rendering:xwiki-rendering-syntax-html5 | before 14.6-rc-1 | 14.6-rc-1 |
| Maven | org.xwiki.rendering:xwiki-rendering-syntax-xhtml | before 14.6-rc-1 | 14.6-rc-1 |
| Maven | org.xwiki.rendering:xwiki-rendering-xml | from 14.6-rc-1 · before 14.10.4 | 14.10.4 |
Same product
xwiki: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-53837org.xwiki.rendering:xwiki-rendering-xml has an Eval Injection issue39Monitor
- CVE-2023-37912XWiki Rendering's footnote macro vulnerable to privilege escalation via the footnote macro35Monitor
- CVE-2025-66474XWiki vulnerable to remote code execution through insufficient protection against {{/html}} injection34Monitor
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-annotation-core | 14.6-rc-1 | Package registry (OSV) |
| Maven:org.xwiki.rendering:xwiki-rendering-syntax-annotatedhtml5 | 14.6-rc-1 | Package registry (OSV) |
| Maven:org.xwiki.rendering:xwiki-rendering-syntax-annotatedxhtml | 14.6-rc-1 | Package registry (OSV) |
| Maven:org.xwiki.rendering:xwiki-rendering-syntax-html | 14.6-rc-1 | Package registry (OSV) |
| Maven:org.xwiki.rendering:xwiki-rendering-syntax-html5 | 14.6-rc-1 | Package registry (OSV) |
| Maven:org.xwiki.rendering:xwiki-rendering-syntax-xhtml | 14.6-rc-1 | Package registry (OSV) |
| Maven:org.xwiki.rendering:xwiki-rendering-xml | 14.10.4 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2025-08-16 |
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.
- Published
- First PoC+660 d
- TodayNov 9, 2026+1111 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-83 · Improper Neutralization of Script in Attributes in a Web PageCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.