LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47324: Silverpeas Core 6.3.1 is vulnerable to Cross Site Scripting (XSS) via the message/notification feature.

Silverpeas Core 6.3.1 is vulnerable to Cross Site Scripting (XSS) via the message/notification feature.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47324 is a reported cross-site scripting issue in Silverpeas Core 6.3.1 involving the message/notification feature. Successful abuse could let attacker-controlled browser content run in a user's Silverpeas session. The source bundle does not provide CVSS, CWE, CPE, or confirmed exploitation data.

Executive priority

Treat this as a targeted application-security fix, not a crisis. Prioritize affected Silverpeas 6.3.1 systems that handle sensitive workflows or broad internal user access, especially where messaging is enabled.

Technical view

The CVE description identifies XSS in Silverpeas Core 6.3.1 through message/notification functionality. Available metadata does not specify whether the flaw is stored or reflected, what privileges are required, or which release contains the fix. Linked sources include Silverpeas Core commits and Rhino Security Labs research.

Likely exposure

Exposure is most likely limited to organizations running Silverpeas Core 6.3.1 where users can access or receive messages/notifications. Broader affected-version scope is unclear because the CVE metadata lists no vendor, product CPE, or version range beyond the description.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Public research exists through the Rhino Security Labs reference, but the bundle does not establish real-world attack activity or exploit maturity.

Researcher notes

Evidence is sparse. The CVE description names Silverpeas Core 6.3.1 and the message/notification feature, but omits CVSS, CWE, CPEs, exploit prerequisites, and fixed-version detail. Avoid expanding affected scope beyond cited sources.

Mitigation direction

  • Identify any Silverpeas Core 6.3.1 deployments.
  • Review Silverpeas project guidance and linked commits for a supported fixed release.
  • Prioritize upgrading if Silverpeas confirms a release containing the fix.
  • Restrict message/notification access to trusted users until remediated.
  • Monitor notifications and related logs for suspicious content.

Validation and detection

  • Confirm installed Silverpeas Core versions across environments.
  • Check whether message/notification functionality is enabled and user-accessible.
  • Review the Silverpeas linked commits for the exact fixed code path.
  • Test remediation with benign XSS validation in an authorized environment.
  • Document compensating controls if upgrade timing is delayed.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-47324 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.