CVE-2023-23851
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSAP 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a file upload vulnerability in SAP Business Planning and Consolidation where improper file format validation allows authenticated attackers to upload arbitrary files, including malicious web pages containing scripts. When other users visit these uploaded pages, the attacker can execute actions in their context (stored XSS), impacting confidentiality and integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 200= 300CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed SAP Business Planning and Consolidation versionCheck the installed version of SAP Business Planning and Consolidation in the system administration console or about page. Compare against the affected versions 200 and 300.Affected if The installed version is exactly 200 or exactly 300.
-
Verify if file upload feature is accessible to authenticated usersLog in as a standard user and navigate to any feature that accepts file uploads (such as document management, attachment upload, or data import functions). Confirm whether the upload interface is present and functional.Affected if The file upload interface is accessible to authenticated users without additional security restrictions.
-
Inspect uploaded file serving behaviorUpload a test file (such as an HTML file or a file with executable extension) through the application. Then attempt to access the uploaded file directly via URL in a web browser to see if it is served with proper Content-Type headers or if it executes/renders in the browser.Affected if Uploaded files are served without proper Content-Type headers or are rendered/executed by the browser instead of being downloaded.
-
Check if HTML file uploads are blockedAttempt to upload a file with .html, .htm, or .xhtml extension containing script content. Observe whether the upload is accepted or rejected by the server.Affected if The server accepts and stores HTML files or files containing script content without validation.
You are affected if your SAP Business Planning and Consolidation version is 200 or 300 AND the file upload feature allows uploading HTML files or serves uploaded files without proper Content-Type headers, enabling stored XSS attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict server-side file format validation that verifies actual file type/content, blocks executable and HTML file uploads, and serves uploaded files with proper headers to prevent script execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23851 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data