How severe is CVE-2023-47323?

CVE-2023-47323 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-47323?

CVE-2023-47323 affects the following packages: org.silverpeas.core:silverpeas-core-api (Maven), org.silverpeas.core:silverpeas-core-web (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-47323?

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 CVE-2023-47323 is resolved across your whole dependency graph.

How do I detect CVE-2023-47323 in my Maven dependencies?

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.

How do I mitigate CVE-2023-47323 if there is no patch (or I can't update yet)?

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.

Is CVE-2023-47323 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-47323, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-47323?

CVE-2023-47323 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2023-47323 published, and has it been updated?

CVE-2023-47323 was published on December 13, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-47323 — silverpeas-core-api

HIGHFix: Silverpeas/Silverpeas-Core@6383746

CVE-2023-47323 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.

Missing access control in Silverpeas

Also known asGHSA-cwh6-hm53-6w2m

Published

Dec 13, 2023

Updated

Oct 28, 2026

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

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

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.silverpeas.core:silverpeas-core-api`	all versions	6.3.2`org.silverpeas.core:silverpeas-core-api:6.3.2`
☕Maven	`org.silverpeas.core:silverpeas-core-web`	all versions	6.3.2`org.silverpeas.core:silverpeas-core-web:6.3.2`

Affected Products

1 product · 1 configurations

Application

silverpeassilverpeas

< 6.3.2

range

Exploits & PoCs

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

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.
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 CVE-2023-47323 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

O3 Security · Impact-Aware SCA

Is CVE-2023-47323 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Dec 13, 2023

First exploit

Dec 15, 2023

3 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2023-47323

GHSA-cwh6-hm53-6w2m

References

Advisorygithub.com · CVE 2023 47323.json Advisorynvd.nist.gov · CVE 2023 47323 Webgithub.com · CVE 2023 47323 Webgithub.com · 6383746372d408eeefa73e17ef95608ddd2c7fba Websilverpeas.com Packagegithub.com · Silverpeas Core

Related vulnerabilities

Also affects silverpeas-core-api

This CVE is high severity — higher than any of the other 1 CVE affecting silverpeas-core-api (highest there: moderate).

CVE-2023-47324

Also affects silverpeas-core-web

This CVE is high severity; 1 of 7 other CVEs affecting silverpeas-core-web is rated as high or higher (top: high).

CVE-2026-30139CVE-2024-39031CVE-2023-47321CVE-2023-47325CVE-2023-47322CVE-2023-47327CVE-2023-47320

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-47323 — silverpeas-core-api

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-47323 in your dependencies?