How severe is GHSA-q6jp-gcww-8v2j?

GHSA-q6jp-gcww-8v2j has a CVSS score of 9.6/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q6jp-gcww-8v2j?

GHSA-q6jp-gcww-8v2j affects the following packages: org.xwiki.platform:xwiki-platform-filter-ui (Maven), org.xwiki.platform:xwiki-platform-filter-ui (Maven), org.xwiki.platform:xwiki-platform-filter-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-q6jp-gcww-8v2j?

Update org.xwiki.platform:xwiki-platform-filter-ui to 13.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6jp-gcww-8v2j is resolved across your whole dependency graph.

How do I detect GHSA-q6jp-gcww-8v2j 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-filter-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q6jp-gcww-8v2j if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-q6jp-gcww-8v2j actively exploited in the wild?

No public exploit code has been indexed for GHSA-q6jp-gcww-8v2j 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-q6jp-gcww-8v2j?

GHSA-q6jp-gcww-8v2j has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th 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-q6jp-gcww-8v2j?

GHSA-q6jp-gcww-8v2j 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-q6jp-gcww-8v2j published, and has it been updated?

GHSA-q6jp-gcww-8v2j was published on November 21, 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

CRITICAL severity

Missing Authorization in Filter Stream Converter Application of XWiki-platformGHSA-q6jp-gcww-8v2j

CRITICALFix: xwiki/xwiki-platform@fb49b4f

GHSA-q6jp-gcww-8v2j is a critical-severity (CVSS 9.6) CWE-862 vulnerability in org.xwiki.platform:xwiki-platform-filter-ui. A fix is available for org.xwiki.platform:xwiki-platform-filter-ui — see the affected versions and patch details below.

Also known asCVE-2022-41937

Published

Nov 21, 2022

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 6, 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-q6jp-gcww-8v2j.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

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

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-filter-ui☕org.xwiki.platform:xwiki-platform-filter-ui☕org.xwiki.platform:xwiki-platform-filter-ui

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 application allow anyone with view access to modify any page of the wiki by importing a crafted XAR package.

Patches

The problem has been patched in XWiki 14.6RC1, 14.6 and 13.10.8.

Workarounds

The problem can be patched immediately by setting the right of the page Filter.WebHome and making sure only main wiki administrators can VIEW it the application is installed on main wiki or edit the page and apply the changed described on https://github.com/xwiki/xwiki-platform/commit/fb49b4f289ee28e45cfada8e97e320cd3ed27113.

References

For more information

If you have any questions or comments about this advisory:

Open an issue in JIRA
Email us at security ML

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-filter-ui`	all versions	13.10.8`org.xwiki.platform:xwiki-platform-filter-ui:13.10.8`
☕Maven	`org.xwiki.platform:xwiki-platform-filter-ui`	≥ 14.0.0&&< 14.4.3	14.4.3`org.xwiki.platform:xwiki-platform-filter-ui:14.4.3`
☕Maven	`org.xwiki.platform:xwiki-platform-filter-ui`	≥ 14.5.0&&< 14.6-rc-1	14.6-rc-1`org.xwiki.platform:xwiki-platform-filter-ui:14.6-rc-1`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 14.0 && < 14.4.3

1 version

14.5

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-filter-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-filter-ui to 13.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q6jp-gcww-8v2j is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact The application allow anyone with view access to modify any page of the wiki by importing a crafted XAR package. ### Patches The problem has been patched in XWiki 14.6RC1, 14.6 and 13.10.8. ### Workarounds The problem can be patched immediately by setting the right of the page Filter.WebHome and making sure only main wiki administrators can VIEW it the application is installed on main wiki or edit the page and apply the changed described on https://github.com/xwiki/xwiki-platform/commit/fb49b4f289ee28e45cfada8e97e320cd3ed27113. ### References * https://github.com/xwiki/xwiki