How severe is GHSA-m5m2-h6h9-p2c8?

GHSA-m5m2-h6h9-p2c8 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-m5m2-h6h9-p2c8?

GHSA-m5m2-h6h9-p2c8 affects the following packages: org.xwiki.platform:xwiki-platform-oldcore (Maven), org.xwiki.platform:xwiki-platform-oldcore (Maven). Ecosystems affected: Maven.

How do I fix GHSA-m5m2-h6h9-p2c8?

Update org.xwiki.platform:xwiki-platform-oldcore to 14.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m5m2-h6h9-p2c8 is resolved across your whole dependency graph.

How do I detect GHSA-m5m2-h6h9-p2c8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m5m2-h6h9-p2c8 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-m5m2-h6h9-p2c8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m5m2-h6h9-p2c8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m5m2-h6h9-p2c8?

GHSA-m5m2-h6h9-p2c8 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 46th 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-m5m2-h6h9-p2c8?

GHSA-m5m2-h6h9-p2c8 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m5m2-h6h9-p2c8 published, and has it been updated?

GHSA-m5m2-h6h9-p2c8 was published on September 4, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Velocity execution without script right through VelocityCode and VelocityWiki propertyGHSA-m5m2-h6h9-p2c8

MEDIUMFix: xwiki/xwiki-platform@edc5257

GHSA-m5m2-h6h9-p2c8 is a medium-severity (CVSS 6.3) CWE-862 vulnerability in org.xwiki.platform:xwiki-platform-oldcore. A fix is available for org.xwiki.platform:xwiki-platform-oldcore — see the affected versions and patch details below.

Also known asCVE-2023-41046

Published

Sep 4, 2023

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m5m2-h6h9-p2c8.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore

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

It is possible in XWiki to execute Velocity code without having script right by creating an XClass with a property of type "TextArea" and content type "VelocityCode" or "VelocityWiki". For the former, the syntax of the document needs to be set the xwiki/1.0 (this syntax doesn't need to be installed). In both cases, when adding the property to an object, the Velocity code is executed regardless of the rights of the author of the property (edit right is still required, though). In both cases, the code is executed with the correct context author so no privileged APIs can be accessed. However, Velocity still grants access to otherwise inaccessible data and APIs that could allow further privilege escalation.

At least for "VelocityCode", this behavior is most likely very old but only since XWiki 7.2, script right is a separate right, before that version all users were allowed to execute Velocity and thus this was expected and not a security issue.

Patches

This has been patched in XWiki 14.10.10 and 15.4 RC1.

Workarounds

There are no known workarounds.

References

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 7.2&&< 14.10.10	14.10.10`org.xwiki.platform:xwiki-platform-oldcore:14.10.10`
☕Maven	`org.xwiki.platform:xwiki-platform-oldcore`	≥ 15.0-rc-1&&< 15.4-rc-1	15.4-rc-1`org.xwiki.platform:xwiki-platform-oldcore:15.4-rc-1`

Affected Products

1 product · 2 configurations

Application

xwikixwiki

≥ 15.0 && < 15.4

range

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.platform:xwiki-platform-oldcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-oldcore to 14.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m5m2-h6h9-p2c8 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### Impact It is possible in XWiki to execute Velocity code without having script right by creating an XClass with a property of type "TextArea" and content type "VelocityCode" or "VelocityWiki". For the former, the syntax of the document needs to be set the `xwiki/1.0` (this syntax doesn't need to be installed). In both cases, when adding the property to an object, the Velocity code is executed regardless of the rights of the author of the property (edit right is still required, though). In both cases, the code is executed with the correct context author so no privileged APIs can be accessed.