Skip to content
Noroxi
CVE-2018-2424· NVD / CVE Program· CNA sap

SAP UI5 did not validate user input before adding it to the DOM structure.

SAP UI5 did not validate user input before adding it to the DOM structure. This may lead to malicious user-provided JavaScript code being added to the DOM that could steal user information. Software components affected are: SAP Hana Database 1.00, 2.00; SAP UI5 1.00; SAP UI5 (Java) 7.30, 7.31, 7.40, 7,50; SAP UI 7.40, 7.50, 7.51, 7.52, and version 2.0 of SAP UI for SAP NetWeaver 7.00

HighCVSS 7.5 · v3.0—No exploit No fix recorded
Published
Jun 12, 2018
Updated
Jun 16, 2026
EPSS
2.4% · 83th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.4%

CNA vs NVD score

NVD
7.5
CNA · sap
9.8
2.3 point gap

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
saphana database
sapui
sapui5
sapui5 java

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • sap hana database1.00
  • sap hana database2.00
  • sap ui2.0
  • sap ui7.40
  • sap ui7.50
  • sap ui7.51
  • sap ui7.52
  • sap ui51.00
  • sap ui5 java7.30
  • sap ui5 java7.31
  • sap ui5 java7.40
  • sap ui5 java7.50

Versions reported by the vendor

Affected version ranges reported by the assigning authority (sap). Independent of NVD's CPE analysis and usually ahead of it.

  • SAP SE SAP HANA Database

    • 1.0, 2.0affected
  • SAP SE SAP UI

    • 7.40, 7.50, 7.51, 7.52affected
  • SAP SE SAP UI for SAP NetWeaver 7.00

    • 2.0affected
  • SAP SE SAP UI5

    • 1.0affected
  • SAP SE SAP UI5(Java)

    • 7.3, 7.31, 7.40, 7.50affected

Same product

sap: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-0492Privilege escalation vulnerability in SAP HANA database
    35Monitor
  • CVE-2019-0350SAP HANA Database, versions 1.0, 2.0, allows an unauthorized attacker to send a malformed connection request, which crashes the indexserver
    30Monitor
  • CVE-2021-21474SAP HANA Database, versions - 1.0, 2.0, accepts SAML tokens with MD5 digest, an attacker who manages to obtain an MD5-digest signed SAML Ass
    26Monitor
  • CVE-2020-26834SAP HANA Database, version - 2.0, does not correctly validate the username when performing SAML bearer token-based user authentication.
    21Monitor
  • CVE-2017-16687The user self-service tools of SAP HANA extended application services, classic user self-service, a part of SAP HANA Database versions 1.00
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

All records