Manufacturing ExecutionApplication · Sap

CVE-2021-27600

MEDIUM · 5.4 CVSS v3.1 Published 2021-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Manufacturing Execution (System Rules), versions - 15.1, 15.2, 15.3, 15.4, allows an authorized attacker to embed malicious code into HTTP parameter and send it to the server because SAP Manufacturing Execution (System Rules) tab does not sufficiently encode some parameters, resulting in Stored Cross-Site Scripting (XSS) vulnerability. The malicious code can be used for different purposes. e.g., information can be read, modified, and sent to the attacker. However, availability of the server cannot be impacted.

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 · moderate confidence

Stored Cross-Site Scripting (XSS) vulnerability in SAP Manufacturing Execution System Rules tab where HTTP parameters are not properly encoded, allowing attackers to inject malicious scripts that persist on the server and execute in other users' browsers.

MitigationApply SAP security patches for CVE-2021-27600 and implement output encoding for System Rules parameters to prevent script injection.

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
Manufacturing ExecutionApplication
Affected:= 15.1= 15.2= 15.3= 15.4

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

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

  1. Identify SAP Manufacturing Execution installation
    Check your system for SAP ME components. On the application server, look for SAP ME web application files in the deployed applications directory (commonly under /sapme* or /SAPME* paths in the web container), or check SAP LM/ME service entries in the system.
    Affected if SAP Manufacturing Execution web application is present and accessible
  2. Verify installed version
    Access the SAP Manufacturing Execution web interface and check the version through the system information page (usually /sapme/webgui or similar endpoint), or check the SAP ME installed software version via SAP LMND (SAP Solution Manager) if available.
    Affected if Version equals 15.1, 15.2, 15.3, or 15.4
  3. Confirm Rules tab is accessible
    Log into the SAP ME web application and navigate to the Rules tab within the system configuration area. Verify the Rules functionality is enabled and accessible to users.
    Affected if The Rules tab is present and users can access it to create or modify rules with HTTP parameters
  4. Inspect HTTP parameter handling in Rules tab
    Use browser developer tools to capture network traffic when submitting data through the Rules tab. Examine the HTTP request parameters sent to the server and check if they are properly encoded or if raw user input appears in the request.
    Affected if User-supplied input in Rules tab parameters is reflected in the response without encoding or sanitization

You are affected if SAP Manufacturing Execution versions 15.1 through 15.4 are installed and the Rules tab with HTTP parameter input is accessible and does not encode user input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches for CVE-2021-27600 and implement output encoding for System Rules parameters to prevent script injection.

Fix this in Manufacturing Execution Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27600 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-27600 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