CVE-2022-24397
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 NetWeaver Enterprise Portal - versions 7.30, 7.31, 7.40, 7.50, does not sufficiently encode user-controlled inputs, resulting in reflected Cross-Site Scripting (XSS) vulnerability.This reflected cross-site scripting attack can be used to non-permanently deface or modify displayed content of portal Website. The execution of the script content by a victim registered on the portal could compromise the confidentiality and integrity of victim’s web browser.
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 confidenceReflected XSS vulnerability in SAP NetWeaver Enterprise Portal versions 7.30 through 7.50 where user-controlled inputs are not properly encoded, allowing attackers to inject malicious scripts that execute in victims' browsers when they access crafted URLs.
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= 7.30= 7.31= 7.40= 7.50CVSS 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.
-
Identify installed SAP NetWeaver Enterprise Portal versionAccess SAP Management Console (SAP MMC) or use SAP transaction code SM51 to display the SAP System Version. Alternatively, check the SAP System Information screen via the SAP Logon pad or web-based SAP System Landscape Directory.Affected if The installed version matches 7.30, 7.31, 7.40, or 7.50 exactly.
-
Confirm Enterprise Portal component is activeVerify that the SAP NetWeaver Enterprise Portal (EP) component is installed and running on the system. Check via SAP MMC under the deployed components or via SAP System Landscape Directory.Affected if The Enterprise Portal component is deployed and running on the affected version.
-
Determine if web-based Portal access is enabledVerify that web access to the Enterprise Portal is enabled by checking the ICM (Internet Communication Manager) configuration via transaction SMICM or by confirming the Portal URL is accessible.Affected if The Portal is accessible via HTTP/HTTPS, providing an attack surface for reflected XSS.
-
Identify exposed Portal endpoints accepting user inputReview the deployed Portal applications and identify URL parameters that accept user input. Common paths include /irj/portal or related EP servlets. Use transaction SIFP to list iViews and their parameters.Affected if User-accessible URL parameters exist that could accept and reflect unsanitized input.
You are affected if SAP NetWeaver Enterprise Portal version 7.30, 7.31, 7.40, or 7.50 is installed with the Portal component active and accessible via web, as the reflected XSS flaw exists in how user-controlled inputs are handled in Portal URLs.
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.
dbcve · scopedApply the SAP security patch for CVE-2022-24397 and implement output encoding for user-controlled inputs on affected endpoints to prevent script injection.
- Check the official SAP Support Portal (launchpad.support.sap.com) for the relevant SAP Security Note addressing CVE-2022-24397
- Apply the security patch or note as specified by SAP for your specific NetWeaver Enterprise Portal version (7.30, 7.31, 7.40, or 7.50)
- After applying the patch, verify that the vulnerability is resolved by testing the affected input fields
- Ensure all subsequent security updates and SAP Notes are applied according to your system's maintenance schedule
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24397 — 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-2022-24397 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