GHSA-v84m-gfw5-hm2w
MEDIUMGHSA-v84m-gfw5-hm2w is a medium-severity (CVSS 6.8) Cross-site Scripting (XSS) vulnerability in org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui. O3 Security confirms whether GHSA-v84m-gfw5-hm2w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Syncope: Reflected XSS on Enduser Login
Real-World Exposure
org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui☕org.apache.syncope.client.idrepo:syncope-client-idrepo-common-uiReal-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
Reflected XSS in Apache Syncope's Enduser Login page.
An attacker that tricks a legitimate user into clicking a malicious link and logging in to Syncope Enduser could steal that user's credentials.
This issue affects Apache Syncope: from 3.0 through 3.0.15, from 4.0 through 4.0.3.
Users are recommended to upgrade to version 3.0.16 / 4.0.4, which fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui | ≥ 3.0.0&&< 3.0.16 | 3.0.16 |
| ☕Maven | org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui | ≥ 4.0.0&&< 4.0.4 | 4.0.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.syncope.client.idrepo:syncope-client-idrepo-common-ui to 3.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v84m-gfw5-hm2w 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.
How O3 protects you
O3 pinpoints whether GHSA-v84m-gfw5-hm2w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-v84m-gfw5-hm2w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v84m-gfw5-hm2w in your dependencies?
O3 detects GHSA-v84m-gfw5-hm2w across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.