Cross Site Request Forgery in Silverpeas

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-47322: 0.39% estimated exploitation activity in the next 30 days; percentile 33.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The "userModify" feature of Silverpeas Core 6.3.1 is vulnerable to Cross Site Request Forgery (CSRF) leading to privilege escalation. If an administrator goes to a malicious URL while being authenticated to the Silverpeas application, the CSRF with execute making the attacker an administrator user in the application.

Published by the source

13 Dec 2023, 15:30 UTC

Last modified by the source

15 Dec 2023, 22:10 UTC

Source last checked

26 Oct 2026, 16:21 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g27c-w2v7-88xp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-47322

Advisory: Cross Site Request Forgery in Silverpeas
IDs: CVE-2023-47322, GHSA-g27c-w2v7-88xp
Record: https://patchnext.com/advisories/cve-2023-47322 (revision 1, source checked 26 Oct 2026, 16:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.silverpeas.core:silverpeas-core-web 6.3.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.silverpeas.core:silverpeas-core-web: affected < 6.3.2; fixed in 6.3.2

## Suggested inspection (read-only)
- Maven org.silverpeas.core:silverpeas-core-web: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.silverpeas.core:silverpeas-core-web.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g27c-w2v7-88xp (GitHub-reviewed advisory GHSA-g27c-w2v7-88xp lists affected ranges: Maven org.silverpeas.core:silverpeas-core-web >=0 <6.3.2)

Commands are suggestions: review each one before running it.