How severe is GHSA-cv2m-5pfp-f245?

No CVSS score has been assigned to GHSA-cv2m-5pfp-f245 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cv2m-5pfp-f245?

GHSA-cv2m-5pfp-f245 affects the following packages: org.silverpeas.core:silverpeas-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cv2m-5pfp-f245?

Update org.silverpeas.core:silverpeas-core to 6.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv2m-5pfp-f245 is resolved across your whole dependency graph.

How do I detect GHSA-cv2m-5pfp-f245 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-cv2m-5pfp-f245 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-cv2m-5pfp-f245?

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

Is GHSA-cv2m-5pfp-f245 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cv2m-5pfp-f245 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cv2m-5pfp-f245?

GHSA-cv2m-5pfp-f245 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 27th 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 GHSA-cv2m-5pfp-f245 published, and has it been updated?

GHSA-cv2m-5pfp-f245 was published on September 2, 2025 and was last updated on September 2, 2025. 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-cv2m-5pfp-f245 — silverpeas-core

Fix: Silverpeas/Silverpeas-Core#1399

GHSA-cv2m-5pfp-f245 is a security vulnerability in org.silverpeas.core:silverpeas-core. A fix is available for org.silverpeas.core:silverpeas-core — see the affected versions and patch details below.

Silverpeas Core Username Enumeration Vulnerability

Also known asCVE-2025-46047

Published

Sep 2, 2025

Updated

Sep 2, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, 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.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cv2m-5pfp-f245.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

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

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

A User enumeration vulnerability in the /CredentialsServlet/ForgotPassword endpoint in Silverpeas 6.4.1 and 6.4.2 allows remote attackers to determine valid usernames via the Login parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.silverpeas.core:silverpeas-core`	≥ 6.4.1&&< 6.4.3	6.4.3`org.silverpeas.core:silverpeas-core:6.4.3`

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.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv2m-5pfp-f245 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-cv2m-5pfp-f245 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cv2m-5pfp-f245. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A User enumeration vulnerability in the /CredentialsServlet/ForgotPassword endpoint in Silverpeas 6.4.1 and 6.4.2 allows remote attackers to determine valid usernames via the Login parameter.

O3 Security · Impact-Aware SCA

Is GHSA-cv2m-5pfp-f245 in your dependencies?

O3 Security finds GHSA-cv2m-5pfp-f245 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