How severe is GHSA-35fg-hjcr-j65f?

GHSA-35fg-hjcr-j65f has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-35fg-hjcr-j65f?

GHSA-35fg-hjcr-j65f affects the following packages: org.xwiki.platform:xwiki-platform-web (Maven), org.xwiki.platform:xwiki-platform-web (Maven), org.xwiki.platform:xwiki-platform-web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-35fg-hjcr-j65f?

Update org.xwiki.platform:xwiki-platform-web to 13.6RC1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35fg-hjcr-j65f is resolved across your whole dependency graph.

How do I detect GHSA-35fg-hjcr-j65f 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-35fg-hjcr-j65f if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-35fg-hjcr-j65f actively exploited in the wild?

No public exploit code has been indexed for GHSA-35fg-hjcr-j65f 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-35fg-hjcr-j65f?

GHSA-35fg-hjcr-j65f has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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-35fg-hjcr-j65f?

GHSA-35fg-hjcr-j65f is classified as Information Exposure (CWE-200), CWE-640 (CWE-640). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-35fg-hjcr-j65f published, and has it been updated?

GHSA-35fg-hjcr-j65f was published on February 9, 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

Information exposure in xwiki-platformGHSA-35fg-hjcr-j65f

MEDIUMFix: xwiki/xwiki-platform@d8a3cce

GHSA-35fg-hjcr-j65f is a medium-severity (CVSS 5.3) Information Exposure vulnerability in org.xwiki.platform:xwiki-platform-web. A fix is available for org.xwiki.platform:xwiki-platform-web — see the affected versions and patch details below.

Also known asCVE-2022-23619

Published

Feb 9, 2022

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-35fg-hjcr-j65f.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-35fg-hjcr-j65f by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-web☕org.xwiki.platform:xwiki-platform-web☕org.xwiki.platform:xwiki-platform-web

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 guess if a user has an account on the wiki by using the "Forgot your password" form, even if the wiki is closed to guest users.

Patches

The problem has been patched on XWiki 12.10.9, 13.4.1 and 13.6RC1.

Workarounds

There's no easy workaround other than applying the upgrade.

References

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

For more information

If you have any questions or comments about this advisory:

Open an issue in JIRA
Email us at XWiki Security Mailing list

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-web`	≥ 13.5RC1&&< 13.6RC1	13.6RC1`org.xwiki.platform:xwiki-platform-web:13.6RC1`
☕Maven	`org.xwiki.platform:xwiki-platform-web`	≥ 13.0.0&&< 13.4.1	13.4.1`org.xwiki.platform:xwiki-platform-web:13.4.1`
☕Maven	`org.xwiki.platform:xwiki-platform-web`	all versions	12.10.9`org.xwiki.platform:xwiki-platform-web:12.10.9`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 13.4.2 && ≤ 13.6

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-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-web to 13.6RC1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35fg-hjcr-j65f is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact It's possible to guess if a user has an account on the wiki by using the "Forgot your password" form, even if the wiki is closed to guest users. ### Patches The problem has been patched on XWiki 12.10.9, 13.4.1 and 13.6RC1. ### Workarounds There's no easy workaround other than applying the upgrade. ### References https://jira.xwiki.org/browse/XWIKI-18787 ### For more information If you have any questions or comments about this advisory: * Open an issue in [JIRA](https://jira.xwiki.org) * Email us at [XWiki Security Mailing list](mailto:[email protected])