NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Missing access control in SilverpeasGHSA-cwh6-hm53-6w2m

HIGHFix: Silverpeas/Silverpeas-Core@6383746

GHSA-cwh6-hm53-6w2m is a high-severity (CVSS 7.5) vulnerability in org.silverpeas.core:silverpeas-core-api. 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-api — see the affected versions and patch details below.

Also known asCVE-2023-47323
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk
0.27%0.61%0.96%1.31%0.8%0.8%May 26Sep 26Nov 26

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

2 pkgs affected
☕org.silverpeas.core:silverpeas-core-api☕org.silverpeas.core:silverpeas-core-web

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

The notification/messaging feature of Silverpeas Core 6.3.1 does not enforce access control on the ID parameter. This allows an attacker to read all messages sent between other users; including those sent only to administrators.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.silverpeas.core:silverpeas-core-apiall versions6.3.2org.silverpeas.core:silverpeas-core-api:6.3.2
☕Mavenorg.silverpeas.core:silverpeas-core-weball versions6.3.2org.silverpeas.core:silverpeas-core-web:6.3.2

Affected Products

1 product · 1 configurations
Application
silverpeassilverpeas
< 6.3.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The notification/messaging feature of Silverpeas Core 6.3.1 does not enf…

github.comNVDDec 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.silverpeas.core:silverpeas-core-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.silverpeas.core:silverpeas-core-api to 6.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cwh6-hm53-6w2m is resolved across your whole dependency graph.

  3. 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

The notification/messaging feature of Silverpeas Core 6.3.1 does not enforce access control on the ID parameter. This allows an attacker to read all messages sent between other users; including those sent only to administrators.
O3 Security · Impact-Aware SCA

Is GHSA-cwh6-hm53-6w2m in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Missing access control in Silverpeas (High 7.5)