dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-44767

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-14
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 5 weeks old

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
setThemeRoot() failed to enforce the sap-allowed-theme-origins allowlist. An attacker-controlled absolute cross-origin URL could be stored and used directly to construct a <link rel=stylesheet> element, even when no <meta name=sap-allowed-theme-origins> tag was present in the document. The same bypass was reachable via the ?sap-themeRoot URL parameter.Exploitation requires attacker-influenced input (e.g., a URL query parameter, tenant configuration, or user-supplied setting) to reach setThemeRoot(). A successful exploit allows an attacker to inject arbitrary CSS into the victim page, enabling:- UI redressing and clickjacking- Phishing overlays- Visual defacement- Limited data exfiltration via CSS attribute selectors targeting predictable DOM content

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 setThemeRoot() function in SAP UI5 failed to enforce the sap-allowed-theme-origins allowlist when no <meta name=sap-allowed-theme-origins> tag existed in the document. This allowed attacker-controlled absolute URLs (via query parameters or tenant configuration) to be used directly in constructing <link rel=stylesheet> elements, enabling CSS injection for clickjacking, phishing, and limited data exfiltration via CSS attribute selectors.

MitigationImplement proper allowlist validation in setThemeRoot() that enforces the sap-allowed-theme-origins configuration even when the meta tag is absent, rejecting any cross-origin URLs not explicitly whitelisted.

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
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 SAP UI5 usage
    Search your codebase for SAP UI5 libraries or check the deployed UI5 version by inspecting the sap-ui-core.js file or checking the sap-ui-version.json endpoint if available
    Affected if UI5 is in use and setThemeRoot() function is being called with user-controlled parameters
  2. Locate setThemeRoot() calls
    Search your codebase for invocations of setThemeRoot() function, particularly those that accept URL parameters from query strings, request parameters, or tenant configuration
    Affected if setThemeRoot() is called with dynamically constructed URLs without server-side validation
  3. Check for sap-allowed-theme-origins meta tag
    Inspect the HTML head section of your application pages for a <meta name='sap-allowed-theme-origins'> tag and verify its content lists the allowed origins
    Affected if The meta tag is missing entirely from the document head
  4. Verify theme root URL origins
    If setThemeRoot() is used, examine what URLs are being passed to it and trace their origin - check if they come from query parameters, API responses, or configuration files that could be controlled by an attacker
    Affected if Cross-origin URLs are passed to setThemeRoot() and no sap-allowed-theme-origins meta tag exists to validate them
  5. Inspect generated link elements
    Examine the rendered HTML in the browser developer tools to see if <link rel=stylesheet> elements are being created with URLs from untrusted origins
    Affected if Stylesheet links point to domains not explicitly listed in the sap-allowed-theme-origins allowlist

You are affected if your SAP UI5 application uses setThemeRoot() with cross-origin URLs but lacks a properly configured sap-allowed-theme-origins meta tag to validate those URLs.

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

Implement proper allowlist validation in setThemeRoot() that enforces the sap-allowed-theme-origins configuration even when the meta tag is absent, rejecting any cross-origin URLs not explicitly whitelisted.

Have this fixed 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-2026-44767 — 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-44767 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