CVE-2021-27615
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 Manufacturing Execution versions - 15.1, 1.5.2, 15.3, 15.4, does not contain some HTTP security headers in their HTTP response. The lack of these headers in response can be exploited by the attacker to execute Cross-Site Scripting (XSS) attacks.
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 confidenceSAP Manufacturing Execution versions 15.1, 1.5.2, 15.3, and 15.4 fail to include essential HTTP security headers in responses. Without headers like Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options, browsers cannot enforce protections against malicious scripts, enabling reflected or stored XSS attacks against users of the application.
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= 15.1= 15.2= 15.3= 15.4CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Manufacturing Execution versionAccess the SAP system administration interface or check the software inventory/bill of materials for SAP Manufacturing Execution. Look for the exact version number in the product information or system details.Affected if The installed version is 15.1, 15.2, 15.3, or 15.4 exactly as listed in the affected versions.
-
Capture HTTP response headers from the applicationUse a browser developer tool (Network tab), curl, or a web proxy to make a request to the SAP Manufacturing Execution web interface and inspect the HTTP response headers.Affected if The response headers do NOT contain Content-Security-Policy, or do NOT contain X-Content-Type-Options, or do NOT contain X-Frame-Options.
-
Verify headers across multiple application endpointsTest several different pages or endpoints within the SAP Manufacturing Execution application (such as login, dashboard, and transaction pages) and check their response headers.Affected if None of the tested endpoints include all three security headers (Content-Security-Policy, X-Content-Type-Options, X-Frame-Options) in their responses.
A user is affected if their SAP Manufacturing Execution version is exactly 15.1, 15.2, 15.3, or 15.4 AND the HTTP responses from the application are missing one or more of the security headers Content-Security-Policy, X-Content-Type-Options, or X-Frame-Options.
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 the SAP security patch for CVE-2021-27615 to add the missing HTTP security headers to all responses, or upgrade to a patched version of SAP Manufacturing Execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27615 — 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-2021-27615 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