CVE-2024-56923 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.silverpeas.core:silverpeas-core. A fix is available for org.silverpeas.core:silverpeas-core — see the affected versions and patch details below.
Cross site scripting in Silverpeas Core
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-56923.
EPSS Exploitation Probability
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
org.silverpeas.core:silverpeas-coreReal-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
Stored Cross-Site Scripting (XSS) Vulnerability in the Categorization Option of My Subscriptions Functionality in Silverpeas Core 6.3.1 <= 6.4.1 allows a remote attacker to execute arbitrary JavaScript code. This is achieved by injecting a malicious payload into the Name field of a subscription. The attack can lead to session hijacking, data theft, or unauthorized actions when an admin user views the affected subscription.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.silverpeas.core:silverpeas-core | ≥ 6.3.1&&< 6.4.2 | 6.4.2org.silverpeas.core:silverpeas-core:6.4.2 |
Affected Products
silverpeassilverpeasDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.silverpeas.core:silverpeas-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.silverpeas.core:silverpeas-core to 6.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-56923 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2024-56923 in your dependencies?
Find it across Maven, including transitive dependencies.