Threats / SAP / CVE-2018-2380
CVE-2018-2380
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
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-034Ransomware use Flagged4EPSS 0.28892 (verify live)5Exploit Weaponized · public PoC6CVSS 6.6 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: partial3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit 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.
Probability (EPSS)
EPSS 0.28892 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.6 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L) · Affected: SAP, Customer Relationship Management (CRM). Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1343 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
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