CVE-2023-24522
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 · uneditedDue to insufficient input sanitization, SAP NetWeaver AS ABAP (Business Server Pages) - versions 700, 701, 702, 731, 740, allows an unauthenticated user to alter the current session of the user by injecting the malicious code over the network and gain access to the unintended data. This may lead to a limited impact on the confidentiality and the integrity of the application.
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 cross-site scripting (XSS) vulnerability in SAP NetWeaver AS ABAP Business Server Pages (BSP). Due to insufficient input sanitization, unauthenticated attackers can inject malicious code over the network to alter user sessions and gain unauthorized access to data.
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= 700= 701= 702= 731= 740CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check SAP NetWeaver AS ABAP versionUse transaction SM51 to view the installed SAP kernel version, or execute transaction SA01 or use the SAP System Information report to confirm the AS ABAP release version (e.g., 700, 701, 702, 731, or 740).Affected if The installed version matches exactly 700, 701, 702, 731, or 740.
-
Verify Business Server Pages (BSP) is enabledUse transaction SICF (SAP Internet Communication Framework) and navigate to the /sap/bc/bsp node path to confirm whether BSP services are active, or check via transaction BSP_MAPPING or by reviewing the ICF tree structure.Affected if BSP services are active and exposed via ICF in the SAP system.
-
Check for exposed BSP applicationsUse transaction SE80 or SICF to list all BSP applications deployed in the system, particularly those accessible over HTTP/HTTPS without authentication.Affected if There are BSP applications that handle user input and are reachable via network requests.
-
Inspect ICF handler configuration for BSPUse transaction SICF to examine the handler assignments for BSP-related ICF nodes, specifically checking if default input validation handlers are configured or if custom handlers are in use.Affected if BSP ICF nodes lack proper input validation handlers or use custom handlers that do not sanitize user input.
A system is affected if it runs SAP NetWeaver AS ABAP version 700, 701, 702, 731, or 740 AND has Business Server Pages enabled and accessible over the network.
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 dataApply the relevant SAP security note/patch for CVE-2023-24522 and implement proper input validation and output encoding in affected Business Server Pages to prevent script injection.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24522 — 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-24522 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