dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-27684

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 NetWeaver Feedback Notifications Service contains a SQL injection vulnerability that allows an authenticated attacker to inject arbitrary SQL code through user-controlled input fields. The application concatenates these inputs directly into SQL queries without proper validation or escaping. As a result, an attacker can manipulate the WHERE clause logic and potentially gain unauthorized access to or modify database information. This vulnerability has no impact on integrity and low impact on the confidentiality and availability of the application.

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

SQL injection vulnerability in SAP NetWeaver Feedback Notifications Service where authenticated attackers can inject arbitrary SQL code through user-controlled input fields that are concatenated directly into SQL queries without proper validation or escaping, allowing manipulation of WHERE clause logic.

MitigationReplace direct SQL concatenation with parameterized queries/prepared statements and implement proper input validation and escaping for all user-controlled fields used in database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L

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 NetWeaver installation and version
    Check for SAP NetWeaver installation directories (typically under /usr/sap or C:\usr\sap on Windows, or use SAP LMDB transaction code). Run transaction code 'SM51' to list installed AS instances and their release versions.
    Affected if SAP NetWeaver is installed and the version falls within the affected range (if known) or if the Feedback Notifications Service component is present.
  2. Verify Feedback Notifications Service is enabled
    Check if the Feedback Notifications Service is active by examining SAP Gateway services (transaction code /IWFND/MAINT_SERVICE) for services related to Feedback or Notification. Also check SAP ICM/ICF services (transaction code SICF) for activated paths under /sap/bc/rest/feedback or similar endpoints.
    Affected if The Feedback Notifications Service is activated and accessible via ICF paths.
  3. Determine network exposure of the service
    Review SAP ICM exposure settings (transaction code SMICM) and firewall rules to determine if the /sap/bc/rest/feedback endpoint is reachable from network segments accessible to untrusted users. Check trust configuration (transaction code STRUSTSSO2).
    Affected if The service is exposed to network segments accessible by authenticated attackers beyond the trusted internal network.
  4. Review access control for the notification service
    Examine SAP Gateway service security settings (transaction code /IWFND/GRMGW) and ICF service authorizations (transaction code SICF, double-click service, check 'Logon Procedure' tab). Determine which users can access the Feedback Notifications Service.
    Affected if Low-privilege or external authenticated users have access to the Feedback Notifications Service endpoints.
  5. Check for SQL concatenation patterns in custom implementations
    If you have access to custom ABAP code interacting with feedback functionality, search for direct SQL concatenation using SE11, SE80, or transaction code CODE_SCANNER. Look for patterns like 'SELECT ... WHERE field = ' & variable or concatenations into WHERE clauses without using parameterized Open SQL.
    Affected if Custom ABAP code uses direct string concatenation to build SQL queries with user input in the feedback notification flow.

You are affected if SAP NetWeaver with Feedback Notifications Service is installed, the service is active, and low-privilege or externally accessible authenticated users can reach the endpoint without proper input validation in the SQL layer.

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

Replace direct SQL concatenation with parameterized queries/prepared statements and implement proper input validation and escaping for all user-controlled fields used in database queries.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27684 — 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-2026-27684 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