CVE-2023-47321 — silverpeas-core-web
MEDIUMCVE-2023-47321 is a medium-severity (CVSS 4.9) vulnerability in org.silverpeas.core:silverpeas-core-web. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.silverpeas.core:silverpeas-core-web — see the affected versions and patch details below.
Broken access control in Silverpeas
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2023-47321.
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-core-webReal-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 Core 6.3.1 is vulnerable to Incorrect Access Control via the "Porlet Deployer" which allows administrators to deploy .WAR portlets.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.silverpeas.core:silverpeas-core-web | all versions | 6.3.2org.silverpeas.core:silverpeas-core-web:6.3.2 |
Affected Products
silverpeassilverpeasResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & 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-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.silverpeas.core:silverpeas-core-web to 6.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-47321 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-2023-47321 in your dependencies?
Find it across Maven, including transitive dependencies.