CVE-2024-36042 is a critical-severity (CVSS 9.8) CWE-288 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.
Silverpeas authentication bypass
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.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-36042.
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
Silverpeas before 6.3.5 allows authentication bypass by omitting the Password field to AuthenticationServlet, often providing an unauthenticated user with superadmin access.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.silverpeas.core:silverpeas-core | all versions | 6.3.5org.silverpeas.core:silverpeas-core:6.3.5 |
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.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-36042 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
Is CVE-2024-36042 in your dependencies?
Find it across Maven, including transitive dependencies.