LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47325: Silverpeas Core 6.3.1 administrative "Bin" feature is affected by broken access control.

Silverpeas Core 6.3.1 administrative "Bin" feature is affected by broken access control. A user with low privileges is able to navigate directly to the bin, revealing all deleted spaces. The user can then restore or permanently delete the spaces.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Silverpeas Core 6.3.1 lets a low-privileged authenticated user directly access the administrative Bin. That can expose deleted spaces and allow restore or permanent deletion, creating confidentiality and integrity risk for collaboration content.

Executive priority

Treat as a moderate priority for Silverpeas environments with many internal users or sensitive collaboration spaces. Prioritize validation and vendor remediation, especially where deleted content may contain regulated or confidential information.

Technical view

The issue is broken access control in the administrative Bin feature. With network access and a low-privileged account, an attacker can bypass intended authorization and view, restore, or permanently delete deleted spaces. CVSS 3.1 is 5.4, with low attack complexity and no user interaction.

Likely exposure

Exposure appears limited to organizations running Silverpeas Core 6.3.1 with untrusted or broadly provisioned authenticated users. The CVE metadata does not provide complete affected CPEs or version ranges.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Public details indicate authenticated misuse rather than unauthenticated compromise. Impact is mainly unauthorized access to deleted spaces and unauthorized restore or deletion actions.

Researcher notes

Public evidence is sparse. The CVE describes the affected feature and behavior, but affected product metadata is incomplete and no patch details are included in the provided sources. Avoid assuming broader version impact without vendor confirmation.

Mitigation direction

  • Check Silverpeas vendor guidance for fixed versions or configuration mitigations.
  • Restrict Silverpeas accounts to trusted users until access control is confirmed.
  • Limit administrative Bin access to authorized administrative roles only.
  • Review logs for unusual Bin access, restore, or permanent deletion events.

Validation and detection

  • Inventory Silverpeas deployments and confirm whether Core 6.3.1 is present.
  • Review role mappings for administrative Bin permissions.
  • Test authorization boundaries in a controlled environment using non-administrative accounts.
  • Confirm deleted spaces cannot be viewed, restored, or deleted by low-privileged users.
Prepared
Confidence
medium
Sources
3

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.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47325 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

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.

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

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-47325Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.