CVE-2022-32247
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, is susceptible to script execution attack by an unauthenticated attacker due to improper sanitization of the User inputs while interacting on the Network. On successful exploitation, an attacker can view or modify information causing a limited impact on confidentiality and 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 confidenceCross-site scripting (XSS) vulnerability in SAP NetWeaver Enterprise Portal versions 7.10-7.50 allows unauthenticated remote attackers to inject malicious scripts through unsanitized user inputs. Successful exploitation enables attackers to execute arbitrary JavaScript in the context of legitimate users' sessions, potentially allowing unauthorized view or modification of application 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= 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.
-
Identify SAP NetWeaver Enterprise Portal installationCheck the SAP system for the presence of SAP NetWeaver Enterprise Portal components. Look for EP (Enterprise Portal) related services or check SAP PAM (Product Availability Matrix) for installed components.Affected if The system has SAP NetWeaver Enterprise Portal installed and the version falls within 7.10 to 7.50.
-
Determine the exact NetWeaver Enterprise Portal versionUse SAP transaction code SPAM or check the SAP system information via SAP MII version info, or inspect the SAP system landscape directory for installed product versions matching the Enterprise Portal component.Affected if The installed version is exactly 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50.
-
Identify user-facing input fields in the portalReview the SAP Enterprise Portal applications and any custom iViews/portlets that accept user input. Check the Portal Content Directory for user-facing components.Affected if User-facing input fields exist in the portal that process and display user-supplied data.
-
Verify input validation and output encodingInspect the source code or configuration of the identified input fields to determine if proper input validation and HTML output encoding are implemented. Look for sanitization functions or security frameworks in use.Affected if Input fields lack proper input validation or output encoding, allowing unsanitized user input to be rendered in HTML responses.
A user is affected if they have SAP NetWeaver Enterprise Portal version 7.10 through 7.50 running with user-facing input fields that do not properly validate or encode user input.
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 proper input validation and output encoding across all user-facing input fields; apply context-aware escaping for user-supplied data before rendering in HTML responses. Consider deploying a web application firewall (WAF) as an interim control.
- Consultation6.0 h
- Implementation16.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32247 — 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-32247 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