basicsecurity.net
Proof, not just disclosure.
Threats / SAP / CVE-2018-2380
CVE-2018-2380 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

SAP Customer Relationship Management (CRM) vulnerability

SAP CRM contains a path traversal vulnerability enabling unauthorized file access through insufficient validation of user-supplied path information.

Verdict

Today item, not a backlog item.

Path traversal in SAP CRM allows attackers to access files outside intended directories. Active exploitation and ransomware deployment have been observed, presenting significant risk to organizations running affected systems.

CISA KEV Yes · 2021-11-033Ransomware use Flagged3EPSS 0.29229 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.29229 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: SAP, Customer Relationship Management (CRM). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious path sequences with directory traversal characters to bypass access controls.
Business
Attackers gain unauthorized access to sensitive files and system resources within the CRM environment.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I extract configuration files, credentials, and business data stored on the affected server.
Business
Confidential customer data, financial records, and authentication credentials are compromised.
3

Lateral reach — past segmentation narrative 3

Attacker
I deploy ransomware payloads or establish persistence mechanisms using the file access capability.
Business
Systems become encrypted or compromised, disrupting CRM operations and triggering incident response costs.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by sap (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by sapCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.