How severe is GHSA-gqgv-7wpj-vm6q?

GHSA-gqgv-7wpj-vm6q has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gqgv-7wpj-vm6q?

GHSA-gqgv-7wpj-vm6q affects the following packages: org.silverpeas.core:silverpeas-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gqgv-7wpj-vm6q?

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

How do I detect GHSA-gqgv-7wpj-vm6q 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gqgv-7wpj-vm6q 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.

Is GHSA-gqgv-7wpj-vm6q actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-gqgv-7wpj-vm6q, 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-gqgv-7wpj-vm6q?

GHSA-gqgv-7wpj-vm6q has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th 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-gqgv-7wpj-vm6q?

GHSA-gqgv-7wpj-vm6q is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gqgv-7wpj-vm6q published, and has it been updated?

GHSA-gqgv-7wpj-vm6q was published on December 13, 2023 and was last updated on December 18, 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

HIGH severity

Cross Site Request Forgery in SilverpeasGHSA-gqgv-7wpj-vm6q

HIGH

GHSA-gqgv-7wpj-vm6q is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in org.silverpeas.core:silverpeas-core. 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 — see the affected versions and patch details below.

Also known asCVE-2023-47326

Published

Dec 13, 2023

Updated

Dec 18, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% 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

1 pkg affected

☕org.silverpeas.core:silverpeas-core

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 Cross Site Request Forgery (CSRF) via the Domain SQL Create function.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.silverpeas.core:silverpeas-core`	all versions	6.3.2`org.silverpeas.core:silverpeas-core: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.

Silverpeas Core 6.3.1 is vulnerable to Cross Site Request Forgery (CSRF)…

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.silverpeas.core:silverpeas-core to 6.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqgv-7wpj-vm6q 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.

Frequently Asked Questions

Silverpeas Core 6.3.1 is vulnerable to Cross Site Request Forgery (CSRF) via the Domain SQL Create function.

O3 Security · Impact-Aware SCA

Is GHSA-gqgv-7wpj-vm6q in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

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 18, 2023

5 days after disclosure — rapid exploitation

Last updated

Dec 18, 2023

Identifiers

GHSA-gqgv-7wpj-vm6q

References

Advisorynvd.nist.gov · CVE 2023 47326 Webgithub.com · CVE 2023 47326 Websilverpeas.com Packagegithub.com · Silverpeas Core

Related vulnerabilities

Also affects silverpeas-core

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

CVE-2026-53698CVE-2025-46047CVE-2024-56923CVE-2024-42850CVE-2024-36042CVE-2024-29392CVE-2023-47326

Same weakness: CWE-352

This CVE is high severity — higher than any of the other 1 CVE with CWE-352 (highest there: low).

CVE-2026-126067Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedDec 18, 2023

Cross Site Request Forgery in SilverpeasGHSA-gqgv-7wpj-vm6q

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 GHSA-gqgv-7wpj-vm6q in your dependencies?