Broken access control in Silverpeas

published 2023-12-13 2 y ago modified 2026-07-09 4 mo ago also GHSA-whgv-6j78-5rh2 , EUVD-2023-3313

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

Silverpeas Core 6.3.1 is vulnerable to Incorrect Access Control. An attacker with low privileges is able to execute the administrator-only function of putting the application in "Maintenance Mode" due to broken access control. This makes the application unavailable to all users. This affects Silverpeas Core 6.3.1 and below.

Patch / fix

fixed in 3 links 1

maven org.silverpeas.core:silverpeas-core-war 6.3.2
maven org.silverpeas.core:silverpeas-core-web 6.3.2
silverpeas silverpeas 6.3.2

github.com/Silverpeas/Silverpeas-Core@fcb4a97 commit

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: total
Assessed: 17 mo ago (2025-05-22)

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/RhinoSecurityLabs/CVEs/tree/master/CVE-2023-47320 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.silverpeas.core:silverpeas-core-war	<6.3.2	6.3.2
maven	org.silverpeas.core:silverpeas-core-web	<6.3.2	6.3.2

Classification

Weakness

CWE-863 Incorrect Authorization
CWE-284 Improper Access Control

References

github.com /Silverpeas/Silverpeas-Core/commit/fcb4a9740b6c80859e435045b549290a82ae84a2
web
github.com /RhinoSecurityLabs/CVEs/tree/master/CVE-2023-47320
web, exploit, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2023-47320
advisory
github.com /Silverpeas/Silverpeas-Core
package
silverpeas.com
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary