dbcve.org
S\/4hanaApplication · Sap

CVE-2023-40306

MEDIUM · 6.1 CVSS v3.1 Published 2023-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Manage Catalog Items and Cross-Catalog searches Fiori apps allow an attacker to redirect users to a malicious site due to insufficient URL validation. As a result, it may have a slight impact on confidentiality and integrity.

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

This is an open redirect vulnerability in SAP S/4HANA's Fiori applications (Manage Catalog Items and Cross-Catalog searches). The apps insufficiently validate URL parameters, allowing attackers to craft malicious links that redirect authenticated users to external phishing or malware sites. The medium severity reflects the limited impact on confidentiality and integrity from a single redirect.

MitigationApply the relevant SAP security note/patch for CVE-2023-40306 and implement URL allowlist validation in the affected Fiori apps to prevent arbitrary redirect targets.

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
S\/4hanaApplication
Affected:= 103= 104= 105= 106

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

CVSS:3.1/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 checks

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

  1. Confirm SAP S/4HANA is deployed
    Identify the SAP system type and ensure it is S/4HANA (not classic SAP ERP). Check system information via transaction SM37 or the SAP System Information app.
    Affected if The system is not SAP S/4HANA (the vulnerability only affects S/4HANA Fiori apps).
  2. Check S/4HANA version number
    Run transaction SM37 and view system details, or use the SAP S/4HANA Migration Cockpit to confirm the version. Look for version 103, 104, 105, or 106 specifically.
    Affected if The installed version is 103, 104, 105, or 106 exactly (these are the affected versions per the CVE).
  3. Verify Fiori launchpad is enabled
    Access the Fiori launchpad URL (typically /sap/bc/ui5_ui5) or check transaction /UI2/FLP to confirm Fiori is active.
    Affected if Fiori launchpad is not enabled or accessible (the vulnerable apps are Fiori applications).
  4. Confirm Manage Catalog Items app is deployed
    Check the Fiori app catalog via transaction /UI2/APPID or access the app directly to see if it exists in the system.
    Affected if The Manage Catalog Items app is installed and accessible (this is one of the two affected Fiori apps).
  5. Confirm Cross-Catalog Search app is deployed
    Check the Fiori app catalog via transaction /UI2/APPID or access Cross-Catalog Search functionality in Fiori to verify availability.
    Affected if The Cross-Catalog Search app is installed and accessible (this is the second affected Fiori app).

If the system is SAP S/4HANA versions 103-106 AND the Fiori launchpad with Manage Catalog Items or Cross-Catalog Search apps is enabled, the environment is potentially affected by this open redirect vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security note/patch for CVE-2023-40306 and implement URL allowlist validation in the affected Fiori apps to prevent arbitrary redirect targets.

Recommended fix Moderate confidence

S/4HANA 2023 or later (or the latest available S/4HANA release)

  1. Check SAP Note for CVE-2023-40306 in the SAP Support Portal (support.sap.com) to obtain the specific patch or configuration guidance
  2. If a patch is available via SAP Note, apply it following SAP's standard patch management procedures
  3. Verify the fix by testing that the Fiori apps Manage Catalog Items and Cross-Catalog searches no longer permit open redirects
  4. Alternatively, upgrade to a later S/4HANA release (e.g., 2023 or later) that includes the security fix
Caveat Review SAP's release notes for any application changes between current version and target version; test custom Fiori extensions for compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in S\/4hana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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