dbcve.org
Sapui5Application · Sap

CVE-2023-30743

MEDIUM · 6.1 CVSS v3.1 Published 2023-05-09
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
Due to improper neutralization of input in SAPUI5 - versions SAP_UI 750, SAP_UI 754, SAP_UI 755, SAP_UI 756, SAP_UI 757, UI_700 200, sap.m.FormattedText SAPUI5 control allows injection of untrusted CSS. This blocks user’s interaction with the application. Further, in the absence of URL validation by the application, the vulnerability could lead to the attacker reading or modifying user’s information through phishing attack.

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

The sap.m.FormattedText control in SAPUI5 versions 750-757 and UI_700 200 improperly neutralizes CSS input, allowing attackers to inject untrusted CSS. This can disrupt user interaction with the application and enable phishing attacks when applications fail to validate URLs embedded in the control.

MitigationUpdate SAPUI5 to a patched version and ensure applications using the FormattedText control implement proper URL validation to prevent phishing vectors.

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
Sapui5Application
Affected:= 700= 750= 754= 755= 756= 757

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. Identify SAPUI5 version
    Locate and inspect the sap-ui-version.js file in your SAPUI5 distribution, or check the sap-ui-version info in the bootstrap script tag of your application
    Affected if The version is 700, 750, 754, 755, 756, or 757 exactly as listed in the affected versions
  2. Confirm sap.m.FormattedText control usage
    Search your application source code for references to sap.m.FormattedText or the XML namespace xmlns:m="sap.m" used in XML views with <FormattedText> elements
    Affected if The FormattedText control is present and used in your application
  3. Check for unsanitized HTML/CSS input
    Examine how the FormattedText control receives data - review any code that sets the htmlText property or binds data to the control, looking for direct insertion of user input without sanitization
    Affected if User-supplied or external data is directly passed to the htmlText property without validation or encoding

Your environment is affected if you run SAPUI5 version 700, 750, 754, 755, 756, or 757 and your application uses the sap.m.FormattedText control with unsanitized input in the htmlText property.

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

Update SAPUI5 to a patched version and ensure applications using the FormattedText control implement proper URL validation to prevent phishing vectors.

Recommended fix Moderate confidence

SAP_UI 757 or latest available SAP_UI version

  1. 1. Identify your current SAPUI5/SAP_UI version from your project's package.json or manifest.json, or check the SAP_UI version in your SAP system.
  2. 2. Check the official SAP Note referenced in launchpad.support.sap.com for this CVE (note number typically included in the SAP security advisory for CVE-2023-30743).
  3. 3. Upgrade your SAP_UI/SAPUI5 dependency to version SAP_UI 757 or higher (the description indicates versions 756 and 757 are also affected, so target the latest stable SAP_UI release beyond 757).
  4. 4. If using UI_700, upgrade to a newer UI_700 patch level or migrate to a higher SAP_UI version.
  5. 5. After upgrading, clear browser caches and test the application to verify the FormattedText control works correctly.
  6. 6. Verify the fix by checking that the CSS injection vulnerability is no longer present in the FormattedText control.
Caveat Review SAP UI add-on release notes for any breaking changes between your current version and the target version; minor version upgrades within the same major release typically have minimal breaking changes.

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

Fix this in Sapui5 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

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