CVE-2022-24395
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.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50, does not sufficiently encode user-controlled inputs, resulting in reflected Cross-Site Scripting (XSS) vulnerability.
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 confidenceSAP NetWeaver Enterprise Portal versions 7.10-7.50 contain a reflected Cross-Site Scripting (XSS) vulnerability due to insufficient encoding of user-controlled inputs. An attacker could craft malicious URLs containing JavaScript code that executes in the context of a victim's browser when clicked, potentially stealing session cookies or performing actions on behalf of the user.
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.10= 7.11= 7.20= 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.
-
Confirm SAP NetWeaver Enterprise Portal is installedIdentify the installed product by checking system information, SAP transaction code SPAM, or consulting SAP system landscape documentation. Look for 'SAP NetWeaver Enterprise Portal' in the installed software inventory.Affected if The product is not SAP NetWeaver Enterprise Portal, then this CVE does not apply.
-
Determine the installed version of SAP NetWeaver Enterprise PortalUse SAP transaction code SM37 or check the SAP System Landscape Directory (SLD). Alternatively, access the SAP Management Console and locate the Enterprise Portal component version information. Compare the version number against the affected list: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50.Affected if The installed version matches exactly one of the following: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50.
-
Verify the vulnerable web component is exposedIdentify if the Enterprise Portal web interfaces (portals/irj/portal or similar URL paths) are accessible externally or internally to users. Check the SAP ICM (Internet Communication Manager) configuration for exposed endpoints that handle user input.Affected if The portal web component is accessible and accepts user-controlled URL parameters.
-
Audit for existing output encodingReview the SAP Enterprise Portal configuration files and custom developed iViews/portlets for output encoding implementation. Examine HTTP response headers for presence of X-XSS-Protection or Content-Security-Policy headers.Affected if No output encoding is implemented on user input handling components and CSP headers are missing or weak.
A user is affected if SAP NetWeaver Enterprise Portal version 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50 is installed and the vulnerable web component that insufficiently encodes user inputs is accessible.
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 available SAP security patches for this vulnerability. As an interim measure, implement output encoding for user-controlled inputs in affected components and configure Content Security Policy headers to mitigate XSS execution.
SAP NetWeaver Enterprise Portal 7.50 or higher (if upgrade path is chosen; newer versions include the fix)
- Check SAP Security Notes for CVE-2022-24395 on the SAP Support Portal (launchpad.support.sap.com)
- Apply the relevant SAP Security Note patch for this XSS vulnerability
- After patching, verify that user-controlled inputs in the Enterprise Portal are properly encoded
- Test the fix by attempting to inject malicious scripts into vulnerable input fields to confirm the XSS is mitigated
- Ensure the SAP NetWeaver Enterprise Portal system is re-tested for any regression issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24395 — 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-24395 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