How severe is GHSA-whgv-6j78-5rh2?

No CVSS score has been assigned to GHSA-whgv-6j78-5rh2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-whgv-6j78-5rh2?

GHSA-whgv-6j78-5rh2 affects the following packages: org.silverpeas.core:silverpeas-core-war (Maven), org.silverpeas.core:silverpeas-core-web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-whgv-6j78-5rh2?

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

How do I detect GHSA-whgv-6j78-5rh2 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-war, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-whgv-6j78-5rh2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-whgv-6j78-5rh2?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-whgv-6j78-5rh2 can be triaged on real exposure rather than presence alone.

Is GHSA-whgv-6j78-5rh2 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-whgv-6j78-5rh2, 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 GHSA-whgv-6j78-5rh2?

GHSA-whgv-6j78-5rh2 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th 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.

What type of vulnerability is GHSA-whgv-6j78-5rh2?

GHSA-whgv-6j78-5rh2 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-whgv-6j78-5rh2 published, and has it been updated?

GHSA-whgv-6j78-5rh2 was published on December 13, 2023 and was last updated on December 13, 2023. 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

GHSA-whgv-6j78-5rh2 — silverpeas-core-war

Fix: Silverpeas/Silverpeas-Core@fcb4a97

GHSA-whgv-6j78-5rh2 is a CWE-863 vulnerability in org.silverpeas.core:silverpeas-core-war. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.silverpeas.core:silverpeas-core-war — see the affected versions and patch details below.

Broken access control in Silverpeas

Also known asCVE-2023-47320

Published

Dec 13, 2023

Updated

Dec 13, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-whgv-6j78-5rh2.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕org.silverpeas.core:silverpeas-core-war☕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

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.

Affected Packages

2 total 2 fixed

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

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.

Silverpeas Core 6.3.1 is vulnerable to Incorrect Access Control. An atta…

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-war, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.silverpeas.core:silverpeas-core-war to 6.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-whgv-6j78-5rh2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-whgv-6j78-5rh2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-whgv-6j78-5rh2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-whgv-6j78-5rh2 in your dependencies?

O3 Security finds GHSA-whgv-6j78-5rh2 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works