How severe is GHSA-m3jr-cvhj-f35j?

GHSA-m3jr-cvhj-f35j has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-m3jr-cvhj-f35j?

GHSA-m3jr-cvhj-f35j affects the following packages: org.xwiki.commons:xwiki-commons-xml (Maven). Ecosystems affected: Maven.

How do I fix GHSA-m3jr-cvhj-f35j?

Update org.xwiki.commons:xwiki-commons-xml to 14.6-rc-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3jr-cvhj-f35j is resolved across your whole dependency graph.

How do I detect GHSA-m3jr-cvhj-f35j in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.commons:xwiki-commons-xml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m3jr-cvhj-f35j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m3jr-cvhj-f35j?

O3 pinpoints whether GHSA-m3jr-cvhj-f35j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m3jr-cvhj-f35j actively exploited in the wild?

Yes. There are 4 known exploit references for GHSA-m3jr-cvhj-f35j, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-m3jr-cvhj-f35j?

GHSA-m3jr-cvhj-f35j has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m3jr-cvhj-f35j?

GHSA-m3jr-cvhj-f35j is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m3jr-cvhj-f35j published, and has it been updated?

GHSA-m3jr-cvhj-f35j was published on April 12, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-m3jr-cvhj-f35j

CRITICAL

org.xwiki.commons:xwiki-commons-xml Cross-site Scripting vulnerability

Also known asCVE-2023-29201

Published

Apr 12, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk63th percentile-8.19%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.xwiki.commons:xwiki-commons-xml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The "restricted" mode of the HTML cleaner in XWiki, introduced in version 4.2-milestone-1, only escaped <script> and <style>-tags but neither attributes that can be used to inject scripts nor other dangerous HTML tags like <iframe>. As a consequence, any code relying on this "restricted" mode for security is vulnerable to JavaScript injection ("cross-site scripting"/XSS). An example are anonymous comments in XWiki where the HTML macro filters HTML using restricted mode:

{{html}}
<a href='' onclick='alert(1)'>XSS</a>
{{/html}}

When a privileged user with programming rights visits such a comment in XWiki, the malicious JavaScript code is executed in the context of the user session. This allows server-side code execution with programming rights, impacting the confidentiality, integrity and availability of the XWiki instance.

Patches

This problem has been patched in XWiki 14.6 RC1 with the introduction of a filter with allowed HTML elements and attributes that is enabled in restricted mode.

Workarounds

There are no known workarounds apart from upgrading to a version including the fix.

References

https://github.com/xwiki/xwiki-commons/commit/b11eae9d82cb53f32962056b5faa73f3720c6182 - the patch with the filter
https://github.com/xwiki/xwiki-commons/commit/4a185e0594d90cd4916d60aa60bb4333dc5623b2 - the patch with the definitions what is allowed
https://jira.xwiki.org/browse/XWIKI-9118 - the security issue with the HTML macro
https://jira.xwiki.org/browse/XCOMMONS-1680 - the issue regarding a definition of what is allowed HTML
https://jira.xwiki.org/browse/XCOMMONS-2426 - the issue regarding the filter that fixes the security issue

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki
Email us at XWiki Security mailing-list

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.commons:xwiki-commons-xml`	≥ 4.2-milestone-1&&< 14.6-rc-1	14.6-rc-1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

XWiki Commons are technical libraries common to several other top level …

jira.xwiki.orgNVDApr 2023

XWiki Commons are technical libraries common to several other top level …

jira.xwiki.orgNVDApr 2023

XWiki Commons are technical libraries common to several other top level …

jira.xwiki.orgNVDApr 2023

XWiki Commons are technical libraries common to several other top level …

github.comNVDApr 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.commons:xwiki-commons-xml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.xwiki.commons:xwiki-commons-xml to 14.6-rc-1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3jr-cvhj-f35j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m3jr-cvhj-f35j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m3jr-cvhj-f35j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The "restricted" mode of the HTML cleaner in XWiki, introduced in version 4.2-milestone-1, only escaped `<script>` and `<style>`-tags but neither attributes that can be used to inject scripts nor other dangerous HTML tags like `<iframe>`. As a consequence, any code relying on this "restricted" mode for security is vulnerable to JavaScript injection ("cross-site scripting"/XSS). An example are anonymous comments in XWiki where the HTML macro filters HTML using restricted mode: ```javascript {{html}} <a href='' onclick='alert(1)'>XSS</a> {{/html}} ``` When a privileged user with pro

O3 Security · Impact-Aware SCA

Is GHSA-m3jr-cvhj-f35j in your dependencies?

O3 detects GHSA-m3jr-cvhj-f35j across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-m3jr-cvhj-f35j

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

References

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-m3jr-cvhj-f35j in your dependencies?