How severe is GHSA-6xxr-648m-gch6?

GHSA-6xxr-648m-gch6 has a CVSS score of 9.6/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6xxr-648m-gch6?

GHSA-6xxr-648m-gch6 affects the following packages: org.xwiki.platform:xwiki-platform-rest-server (Maven), com.xpn.xwiki.platform:xwiki-core-rest-server (Maven), com.xpn.xwiki.platform:xwiki-rest (Maven), org.xwiki.platform:xwiki-platform-rest-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6xxr-648m-gch6?

Update org.xwiki.platform:xwiki-platform-rest-server to 14.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xxr-648m-gch6 is resolved across your whole dependency graph.

How do I detect GHSA-6xxr-648m-gch6 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-rest-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6xxr-648m-gch6 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.

Is GHSA-6xxr-648m-gch6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6xxr-648m-gch6 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-6xxr-648m-gch6?

GHSA-6xxr-648m-gch6 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th 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-6xxr-648m-gch6?

GHSA-6xxr-648m-gch6 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6xxr-648m-gch6 published, and has it been updated?

GHSA-6xxr-648m-gch6 was published on July 10, 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

CRITICAL severity

XWiki Platform vulnerable to cross-site request forgery (CSRF) via the REST APIGHSA-6xxr-648m-gch6

CRITICALFix: xwiki/xwiki-platform@4c17540

GHSA-6xxr-648m-gch6 is a critical-severity (CVSS 9.6) Cross-Site Request Forgery (CSRF) vulnerability in org.xwiki.platform:xwiki-platform-rest-server. A fix is available for org.xwiki.platform:xwiki-platform-rest-server — see the affected versions and patch details below.

Also known asCVE-2023-37277

Published

Jul 10, 2023

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6xxr-648m-gch6.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% 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

4 pkgs affected

☕org.xwiki.platform:xwiki-platform-rest-server☕com.xpn.xwiki.platform:xwiki-core-rest-server☕com.xpn.xwiki.platform:xwiki-rest☕org.xwiki.platform:xwiki-platform-rest-server

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 REST API allows executing all actions via POST requests and accepts text/plain, multipart/form-data or application/www-form-urlencoded as content types which can be sent via regular HTML forms, thus allowing cross-site request forgery. With the interaction of a user with programming rights, this allows remote code execution through script macros and thus impacts the integrity, availability and confidentiality of the whole XWiki installation.

For regular cookie-based authentication, the vulnerability is mitigated by SameSite cookie restrictions but as of March 2023, these are not enabled by default in Firefox and Safari.

Patches

The vulnerability has been patched in XWiki 14.10.8 and 15.2 by requiring a CSRF token header for certain request types that are susceptible to CSRF attacks.

Workarounds

It is possible to check for the Origin header in a reverse proxy to protect the REST endpoint from CSRF attacks, see the Jira issue for an example configuration.

References

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 1.8&&< 14.10.8	14.10.8`org.xwiki.platform:xwiki-platform-rest-server:14.10.8`
☕Maven	`com.xpn.xwiki.platform:xwiki-core-rest-server`	≥ 1.8&&< 14.10.8	14.10.8`com.xpn.xwiki.platform:xwiki-core-rest-server:14.10.8`
☕Maven	`com.xpn.xwiki.platform:xwiki-rest`	≥ 1.8&&< 14.10.8	14.10.8`com.xpn.xwiki.platform:xwiki-rest:14.10.8`
☕Maven	`org.xwiki.platform:xwiki-platform-rest-server`	≥ 15.0-rc-1&&< 15.2	15.2`org.xwiki.platform:xwiki-platform-rest-server:15.2`

Affected Products

1 product · 2 configurations

Application

xwikixwiki

≥ 15.0 && < 15.2

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-rest-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-rest-server to 14.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xxr-648m-gch6 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.

Frequently Asked Questions

### Impact The REST API allows executing all actions via POST requests and accepts `text/plain`, `multipart/form-data` or `application/www-form-urlencoded` as content types which can be sent via regular HTML forms, thus allowing cross-site request forgery. With the interaction of a user with programming rights, this allows remote code execution through script macros and thus impacts the integrity, availability and confidentiality of the whole XWiki installation. For regular cookie-based authentication, the vulnerability is mitigated by SameSite cookie restrictions but as of March 2023, these