dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-44744

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 S/4HANA(On-Premise) contains SQL injection vulnerability in a remote-enabled function module component that could be exploited by an authenticated attacker to potentially execute unauthorized database queries.This flaw exposes sensitive information to which they should not otherwise have access to. The vulnerability has a high impact on the confidentiality of the data with no impact on the integrity 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 · high confidence

SQL injection vulnerability in SAP S/4HANA (On-Premise) remote-enabled function module allows authenticated attackers to execute unauthorized database queries, exposing sensitive data they should not access. The vulnerability has high confidentiality impact but no impact on integrity or availability.

MitigationApply SAP security patches for CVE-2026-44744 and review access controls on remote-enabled function modules to restrict to authorized users only.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm SAP S/4HANA On-Premise deployment
    Run transaction SM51 or check system information via SAP Logon to verify you are on S/4HANA On-Premise (not Cloud or Hybrid)
    Affected if System is identified as S/4HANA On-Premise edition - the vulnerability applies only to on-premise deployments
  2. Identify remote-enabled function modules
    Use transaction SE37 or SE80 to list function modules with 'Remote-Enabled' (RFC) attribute active. Focus on modules handling database query operations or data retrieval functions.
    Affected if Function modules with RFC capability are exposed to network attack surface; remote-enabled modules are required for this exploit
  3. Locate function modules with database query logic
    Search ABAP code using transaction SE80 or code search (e.g., ADT, transaction CODE_SCANNER) for function modules executing Open SQL or Native SQL statements (SELECT, INSERT, UPDATE, DELETE)
    Affected if Function modules containing direct SQL execution logic are potential vectors for SQL injection if input is not parameterized
  4. Review ABAP code for unsanitized input in SQL statements
    Inspect the ABAP source code of remote-enabled function modules. Look for dynamic SQL construction (e.g., EXECUTE STATEMENT, CONCATENATE with SQL fragments) where input parameters are used directly without proper escaping or parameterization.
    Affected if Code contains dynamic SQL using concatenated user input or parameters without ABAP SQL API parameterization - this is the vulnerable pattern
  5. Verify user access control on function modules
    Check transaction SU01 or role definitions (PFCG) to review which authenticated users have execution rights to the remote-enabled function modules identified. Excessive permissions increase exposure risk.
    Affected if Users beyond strict necessity have RFC execution authorizations to vulnerable function modules

If running SAP S/4HANA On-Premise with remote-enabled function modules containing unsanitized SQL query logic accessible to authenticated users, the environment is likely affected by this CVE.

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-2026-44744 and review access controls on remote-enabled function modules to restrict to authorized users only.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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