LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23851: SAP Business Planning and Consolidation - versions 200, 300, allows an attacker with business authorization...

SAP Business Planning and Consolidation - versions 200, 300, allows an attacker with business authorization to upload any files (including web pages) without the proper file format validation. If other users visit the uploaded malicious web page, the attacker may perform actions on behalf of the users without their consent impacting the confidentiality and integrity of the system.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

SAP Business Planning and Consolidation versions 200 and 300 allowed authorized business users to upload files without proper format checks. A malicious uploaded web page could trick another user into visiting it and then cause actions under that user’s session, affecting confidentiality and integrity.

Executive priority

Treat as a moderate-priority SAP application risk. It needs timely remediation where SAP BPC is used for sensitive planning or consolidation data, especially if many business users can upload shared content.

Technical view

This is CWE-434 unrestricted upload with CVSS 3.1 score 5.4. The vector indicates network reachability, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, and no availability impact.

Likely exposure

Exposure is limited to SAP Business Planning and Consolidation version 200 or 300 where business-authorized users can upload content. Systems without these versions, without the vulnerable upload workflow, or with vendor fixes applied are less likely exposed.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires an attacker with business authorization and a victim user who visits the uploaded malicious web page. The impact is session-mediated action without consent, not unauthenticated remote takeover.

Researcher notes

Evidence is limited to the CVE description, CVSS data, CWE-434 classification, affected SAP BPC versions, and SAP references. The source bundle does not provide exploit details, patch mechanics, or confirmed exploitation activity.

Mitigation direction

  • Review SAP Security Note 3275841 and apply vendor guidance for affected systems.
  • Restrict upload permissions to users with a clear business need.
  • Audit existing uploaded files and remove unexpected web pages or active content.
  • Monitor SAP BPC activity for unusual uploads or user actions after viewing uploaded content.

Validation and detection

  • Inventory SAP BPC deployments and confirm whether versions 200 or 300 are present.
  • Verify patch or configuration status against SAP Security Note 3275841.
  • Review roles that grant business authorization for file upload workflows.
  • Confirm server-side upload validation rejects unexpected web-page file types.
  • Check logs for suspicious uploads and subsequent actions by other users.
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.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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-23851 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:R/S:C/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
0Timeline events
0ADP providers
3Source links

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:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SAPBusiness Planning and Consolidation200, 300unaffected
Weakness

CWE details

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

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.