How severe is GHSA-fxwr-4vq9-9vhj?

GHSA-fxwr-4vq9-9vhj has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-fxwr-4vq9-9vhj?

GHSA-fxwr-4vq9-9vhj affects the following packages: org.xwiki.platform:xwiki-platform-web-templates (Maven), org.xwiki.platform:xwiki-platform-web-templates (Maven). Ecosystems affected: Maven.

How do I fix GHSA-fxwr-4vq9-9vhj?

Update org.xwiki.platform:xwiki-platform-web-templates to 13.10.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fxwr-4vq9-9vhj is resolved across your whole dependency graph.

How do I detect GHSA-fxwr-4vq9-9vhj 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-web-templates, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fxwr-4vq9-9vhj 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-fxwr-4vq9-9vhj actively exploited in the wild?

No public exploit code has been indexed for GHSA-fxwr-4vq9-9vhj 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-fxwr-4vq9-9vhj?

GHSA-fxwr-4vq9-9vhj has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th 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-fxwr-4vq9-9vhj?

GHSA-fxwr-4vq9-9vhj 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-fxwr-4vq9-9vhj published, and has it been updated?

GHSA-fxwr-4vq9-9vhj was published on September 16, 2022 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

Not in CISA KEV

MEDIUM severity

XWiki Cross-Site Request Forgery (CSRF) for actions on tagsGHSA-fxwr-4vq9-9vhj

MEDIUMFix: xwiki/xwiki-platform@7ca56e4

GHSA-fxwr-4vq9-9vhj is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in org.xwiki.platform:xwiki-platform-web-templates. A fix is available for org.xwiki.platform:xwiki-platform-web-templates — see the affected versions and patch details below.

Also known asCVE-2022-36095

Published

Sep 16, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-fxwr-4vq9-9vhj.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs37th percentile — riskier than 37% 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-web-templates☕org.xwiki.platform:xwiki-platform-web-templates

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's possible to perform a CSRF attack for adding or removing tags on XWiki pages.

Patches

The problem has been patched in XWiki 13.10.5 and 14.3.

Workarounds

It's possible to fix the issue without upgrading by locally modifying the documentTags.vm template in your filesystem, to apply the changes exposed there: https://github.com/xwiki/xwiki-platform/commit/7ca56e40cf79a468cea54d3480b6b403f259f9ae.

References

https://jira.xwiki.org/browse/XWIKI-19550

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki
Email us at security ML

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-web-templates`	≥ 2.0-milestone-1&&< 13.10.5	13.10.5`org.xwiki.platform:xwiki-platform-web-templates:13.10.5`
☕Maven	`org.xwiki.platform:xwiki-platform-web-templates`	≥ 14.0&&< 14.3	14.3`org.xwiki.platform:xwiki-platform-web-templates:14.3`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 14.0 && < 14.3

1 version

2.0

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-web-templates, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-web-templates to 13.10.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fxwr-4vq9-9vhj 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 It's possible to perform a CSRF attack for adding or removing tags on XWiki pages. ### Patches The problem has been patched in XWiki 13.10.5 and 14.3. ### Workarounds It's possible to fix the issue without upgrading by locally modifying the documentTags.vm template in your filesystem, to apply the changes exposed there: https://github.com/xwiki/xwiki-platform/commit/7ca56e40cf79a468cea54d3480b6b403f259f9ae. ### References https://jira.xwiki.org/browse/XWIKI-19550 ### For more information If you have any questions or comments about this advisory: * Open an issue in [Jira XWiki]