CVE-2016-1911
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in SAP NetWeaver 7.4 allow remote attackers to inject arbitrary web script or HTML via vectors related to the (1) Runtime Workbench (RWB) or (2) Pmitest servlet in the Process Monitoring Infrastructure (PMI), aka SAP Security Notes 2206793 and 2234918.
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) vulnerabilities in SAP NetWeaver 7.4 allow remote attackers to inject arbitrary web script or HTML through the Runtime Workbench (RWB) and Pmitest servlet in the Process Monitoring Infrastructure (PMI). The vulnerabilities are tracked in SAP Security Notes 2206793 and 2234918.
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.40CVSS 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.
-
Verify SAP NetWeaver versionAccess SAP NetWeaver Administrator or use transaction SM37 to check system version. Alternatively, check the SAP system info via /n/iwfnd/maint_service or SAP MII transaction.Affected if Installed version is exactly SAP NetWeaver 7.40 (7.4)
-
Confirm Runtime Workbench (RWB) is deployedAccess the Runtime Workbench via web browser at the standard endpoint (typically /RWB or /rwba) or check deployment via SAP NetWeaver Administrator under Web Services.Affected if Runtime Workbench is accessible and responds to requests on the system
-
Confirm PMI Pmitest servlet is exposedAccess the Pmitest servlet endpoint via web browser (typically under the Process Monitoring Infrastructure path) or check servlet configuration in the SAP web container.Affected if The Pmitest servlet is accessible and responds to HTTP requests
-
Test for XSS in Runtime WorkbenchSubmit a test XSS payload such as <script>alert('XSS')</script> to input fields within the Runtime Workbench interface and observe if the script executes in the response.Affected if The submitted script or HTML is reflected unencoded in the Runtime Workbench response
-
Test for XSS in PMI Pmitest servletSubmit a test XSS payload such as <script>alert('XSS')</script> to parameters in the Pmitest servlet URL and observe if the script executes in the response.Affected if The submitted script or HTML is reflected unencoded in the Pmitest servlet response
A system is affected if it runs SAP NetWeaver 7.40 with either the Runtime Workbench or PMI Pmitest servlet exposed and unpatched by SAP Security Notes 2206793 and 2234918, and XSS payloads are reflected without 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.
From vendor dataApply SAP Security Notes 2206793 and 2234918 to patch the XSS vulnerabilities in the Runtime Workbench and PMI Pmitest servlet. Implement output encoding and input validation as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1911 — 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-2016-1911 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