dbcve.org
Enterprise PortalApplication · Sap

CVE-2022-35224

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
SAP 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 Cross-Site Scripting (XSS) vulnerability. This attack can be used to non-permanently deface or modify portal content. The execution of script content by a victim registered on the portal could compromise the confidentiality and integrity of victim�s web browser 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 confidence

SAP Enterprise Portal versions 7.10 through 7.50 contain a reflected Cross-Site Scripting (XSS) vulnerability due to insufficient encoding of user-controlled inputs. Attackers can inject malicious scripts that execute in the browsers of authenticated portal users, potentially allowing session hijacking, content manipulation, or theft of credentials.

MitigationApply the relevant SAP security patch for CVE-2022-35224 and implement proper input validation and output encoding for all user-supplied data. Conduct thorough testing to confirm the fix addresses all affected parameters.

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
Enterprise PortalApplication
Affected:= 7.10= 7.11= 7.20= 7.30= 7.31= 7.40= 7.50

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SAP Enterprise Portal installation and version
    Locate the SAP Enterprise Portal installation directory or use SAP transaction code SM37 to identify the running EP version. Check the system information via SAP Management Console or the SAP NetWeaver Administrator (NWA) portal at /nwa. Navigate to Configuration -> System Information to find the installed EP version number.
    Affected if The installed version matches 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50.
  2. Confirm the vulnerable version range
    Compare your identified SAP Enterprise Portal version against the affected range: versions 7.10 through 7.50. This includes all minor releases: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, and 7.50.
    Affected if Your version is exactly one of: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50.
  3. Identify user-controlled input parameters
    Review web application firewall logs, SAP Enterprise Portal access logs, or HTTP traffic to identify URL parameters and form inputs that accept user-supplied data and reflect them back in responses without encoding. Focus on search fields, navigation parameters, and URL query strings.
    Affected if The portal accepts and reflects user-supplied input in HTTP responses without proper HTML encoding.
  4. Verify authentication context for the vulnerable endpoint
    Determine whether the reflected XSS payload would be delivered to authenticated users. Review the vulnerable URL parameter context to confirm it is accessible within authenticated portal sessions. This is a reflected XSS requiring authenticated users to trigger the malicious script.
    Affected if The vulnerable parameter is accessible within authenticated SAP Enterprise Portal user sessions.

You are affected if your SAP Enterprise Portal version is exactly 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50 and user-controlled input is reflected in responses without encoding to authenticated portal users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for CVE-2022-35224 and implement proper input validation and output encoding for all user-supplied data. Conduct thorough testing to confirm the fix addresses all affected parameters.

Recommended fix Moderate confidence
  1. Check SAP Launchpad (launchpad.support.sap.com) for Security Note related to CVE-2022-35224
  2. Log into SAP Support Portal and search for the relevant SAP Enterprise Portal security patch
  3. Download the patch following SAP's standard patch application procedures
  4. Apply the patch to the affected SAP Enterprise Portal system following SAP's implementation guide
  5. After applying the patch, verify the fix by testing that user-controlled inputs are properly encoded and XSS is no longer possible
  6. Clear browser cache and test with a non-persistent XSS proof-of-concept to confirm remediation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Portal Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35224 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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