How severe is GHSA-pg4m-3gp6-hw4w?

GHSA-pg4m-3gp6-hw4w 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-pg4m-3gp6-hw4w?

GHSA-pg4m-3gp6-hw4w affects the following packages: org.xwiki.platform:xwiki-platform-notifications-ui (Maven), org.xwiki.platform:xwiki-platform-notifications-ui (Maven), org.xwiki.platform:xwiki-platform-notifications-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pg4m-3gp6-hw4w?

Update org.xwiki.platform:xwiki-platform-notifications-ui to 14.10.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pg4m-3gp6-hw4w is resolved across your whole dependency graph.

How do I detect GHSA-pg4m-3gp6-hw4w 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-notifications-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pg4m-3gp6-hw4w 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-pg4m-3gp6-hw4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-pg4m-3gp6-hw4w 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-pg4m-3gp6-hw4w?

GHSA-pg4m-3gp6-hw4w 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-pg4m-3gp6-hw4w?

GHSA-pg4m-3gp6-hw4w is classified as Information Exposure (CWE-200), CWE-359 (CWE-359). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pg4m-3gp6-hw4w published, and has it been updated?

GHSA-pg4m-3gp6-hw4w was published on September 18, 2024 and was last updated on September 18, 2024. 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

org.xwiki.platform:xwiki-platform-notifications-ui leaks data of notification filters of usersGHSA-pg4m-3gp6-hw4w

MEDIUMFix: xwiki/xwiki-platform@29e5edb

GHSA-pg4m-3gp6-hw4w is a medium-severity (CVSS 5.3) Information Exposure vulnerability in org.xwiki.platform:xwiki-platform-notifications-ui. A fix is available for org.xwiki.platform:xwiki-platform-notifications-ui — see the affected versions and patch details below.

Also known asCVE-2024-46979

Published

Sep 18, 2024

Updated

Sep 18, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 7, 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-pg4m-3gp6-hw4w.

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

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-notifications-ui☕org.xwiki.platform:xwiki-platform-notifications-ui☕org.xwiki.platform:xwiki-platform-notifications-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

It's possible to get access to notification filters of any user by using a URL such as <hostname>xwiki/bin/get/XWiki/Notifications/Code/NotificationFilterPreferenceLivetableResults?outputSyntax=plain&type=custom&user=<username>. This vulnerability impacts all versions of XWiki since 13.2-rc-1. The filters do not provide much information (they mainly contain references which are public data in XWiki), though some info could be used in combination with other vulnerabilities.

Patches

The vulnerability has been patched in XWiki 14.10.21, 15.5.5, 15.10.1, 16.0RC1. The patch consists in checking the rights of the user when sending the data.

Workarounds

It's possible to workaround the vulnerability by applying manually the patch: it's possible for an administrator to edit directly the document XWiki.Notifications.Code.NotificationFilterPreferenceLivetableResults to apply the same changes as in the patch. See c8c6545f9bde6f5aade994aa5b5903a67b5c2582.

References

Jira ticket: https://jira.xwiki.org/browse/XWIKI-20336
Commit: c8c6545f9bde6f5aade994aa5b5903a67b5c2582

For more information

If you have any questions or comments about this advisory:

Open an issue in Jira XWiki.org
Email us at Security Mailing List

Attribution

This vulnerability has been reported on Intigriti by Mete.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-notifications-ui`	≥ 13.2-rc-1&&< 14.10.21	14.10.21`org.xwiki.platform:xwiki-platform-notifications-ui:14.10.21`
☕Maven	`org.xwiki.platform:xwiki-platform-notifications-ui`	≥ 15.0-rc-1&&< 15.5.5	15.5.5`org.xwiki.platform:xwiki-platform-notifications-ui:15.5.5`
☕Maven	`org.xwiki.platform:xwiki-platform-notifications-ui`	≥ 15.6-rc-1&&< 15.10.1	15.10.1`org.xwiki.platform:xwiki-platform-notifications-ui:15.10.1`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 15.6 && < 15.10.1

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-notifications-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-notifications-ui to 14.10.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pg4m-3gp6-hw4w 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 get access to notification filters of any user by using a URL such as `<hostname>xwiki/bin/get/XWiki/Notifications/Code/NotificationFilterPreferenceLivetableResults?outputSyntax=plain&type=custom&user=<username>`. This vulnerability impacts all versions of XWiki since 13.2-rc-1. The filters do not provide much information (they mainly contain references which are public data in XWiki), though some info could be used in combination with other vulnerabilities. ### Patches The vulnerability has been patched in XWiki 14.10.21, 15.5.5, 15.10.1, 16.0RC1. The patch con