CVE-2018-2435
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 from 7.0 to 7.02, 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.
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Enterprise Portal versions 7.0 through 7.50 where user-supplied input is not properly encoded before being rendered in web pages, allowing execution of arbitrary JavaScript in victim browsers.
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.0, <= 7.02= 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.0/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 or use transaction code SM37 to view system information, or check the SAP NetWeaver Administrator (NWA) interface under System Information for the exact portal version numberAffected if The displayed version matches any of: 7.0, 7.01, 7.02, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50 (versions >= 7.0 through 7.50)
-
Verify web portal is accessibleAttempt to access the Enterprise Portal login page via browser at the standard portal URL (typically /irj/portal or /webdynpro/dispatcher/sap.com/tc~lm~wd~ads~wdads), or confirm the SAP HTTP service is running via SAP Management ConsoleAffected if The Enterprise Portal web interface is reachable and operational
-
Inspect for unencoded user input fieldsLog into the portal and navigate to user profile or content creation areas where user-supplied data can be saved and displayed (such as document management, collaboration rooms, or user profile fields), then view the page source of rendered content to check if special characters are being output-encodedAffected if User-controlled input is rendered in HTML without proper encoding (visible <script> tags or unescaped < > characters in the page source indicate the vulnerability may be present)
A user is affected if they are running SAP NetWeaver Enterprise Portal versions 7.0 through 7.50 AND have the web portal interface exposed, with user input fields that are not properly HTML-encoded when rendered.
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 dataApply SAP security patches/notes for CVE-2018-2435 and implement proper output encoding for all user-controlled inputs in the affected portal components.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2435 — 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-2018-2435 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