CVE-2022-35227
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 · uneditedA vulnerability in SAP NW EP (WPC) - versions 7.30, 7.31, 7.40, 7.50, which does not sufficiently validate user-controlled input, allows a remote attacker to conduct a Cross-Site (XSS) scripting attack. A successful exploit could allow the attacker to execute arbitrary script code which could lead to stealing or modifying of authentication information of the user, such as data relating to his or her current session.
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 confidenceA reflected XSS vulnerability in SAP NetWeaver Enterprise Portal Workplace (WPC) versions 7.30-7.50 allows remote attackers to inject malicious script code through insufficiently validated user input. The flaw enables execution of arbitrary JavaScript in victims' browsers, facilitating session hijacking and theft of authentication credentials.
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 SAP NetWeaver Enterprise Portal versionAccess the SAP Enterprise Portal system information page (typically via SAP GUI transaction SPAM or the portal's system info page). Alternatively, check the installed product version through the SAP Support Portal or the system's software catalog.Affected if The installed version matches 7.30, 7.31, 7.40, or 7.50 exactly.
-
Confirm Workplace (WPC) component is deployedVerify that the Workplace (WPC) component is installed and enabled on the SAP Enterprise Portal. This can be done by checking the portal's system configuration or by attempting to access the Workplace URL (typically /irj/portal).Affected if The Workplace (WPC) component is deployed and accessible on the portal.
-
Verify vulnerable endpoint accessibilityDetermine if the portal's Workplace (WPC) functionality is accessible to unauthenticated or low-privilege users through the web interface. Check if user input parameters in the Workplace URL can be manipulated.Affected if The WPC endpoint accepts user-controlled input without sufficient validation.
-
Inspect HTTP response for input reflectionIf you have access to the affected system, send a crafted request with a test payload (such as a benign script tag) to the Workplace endpoint and observe if the input is reflected back in the HTTP response without proper encoding.Affected if User-supplied input is reflected in the response without HTML encoding.
A system is affected if it runs SAP NetWeaver Enterprise Portal version 7.30, 7.31, 7.40, or 7.50 with the Workplace (WPC) component enabled and accessible, and user input is reflected in web pages without proper encoding.
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 · scopedImplement proper input validation and output encoding for all user-controlled data rendered in web pages. Apply context-aware sanitization and consider deploying Content Security Policy headers to mitigate XSS impact.
Apply the SAP Security Note for CVE-2022-35227 - contact SAP for the specific patch number and request the relevant support package update for your NetWeaver EP version
- 1. Access the SAP Support Portal at https://launchpad.support.sap.com/
- 2. Search for SAP Security Note number corresponding to CVE-2022-35227
- 3. Download and review the applicable SAP Note/Patch for your specific NetWeaver EP version (7.30, 7.31, 7.40, or 7.50)
- 4. Apply the security patch following SAP's standard patch deployment procedures
- 5. Verify the patch has been applied successfully by checking the WPC component version
- 6. Test the fix by attempting to inject script content in the identified input fields to confirm XSS is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35227 — 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-35227 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