Threats / SAP / CVE-2020-6287
CVE-2020-6287
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
SAP NetWeaver vulnerability
SAP NetWeaver Application Server Java lacks authentication for critical functions, allowing unauthenticated attackers to execute configuration tasks and create administrative users.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can bypass access controls to perform privileged administrative operations on affected SAP NetWeaver systems, leading to complete compromise of the application server and hosted business processes.
CISA KEV Yes · 2021-11-035EPSS 0.94719 (verify live)6Exploit Weaponized · public PoC7CVSS 103CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
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
578 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).
Probability (EPSS)
EPSS 0.94719 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 10 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: SAP, NetWeaver. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-306 Missing Authentication — weakness family: Authentication.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: yes · Technical Impact: totalCISA'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 477 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.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
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 access the NetWeaver application server without credentials by targeting the unauthenticated critical function endpoint.
Business
The organization loses network perimeter security as the application server becomes accessible to any remote actor.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute configuration tasks through the exposed functions to modify system settings and security policies.
Business
System integrity is compromised as attackers alter configurations to maintain persistence and expand their access.
3
Lateral reach — past segmentation narrative 3
Attacker
I create new administrative user accounts with full privileges to establish persistent backdoor access.
Business
Attackers gain permanent control over the SAP environment, enabling data theft, manipulation, and operational disruption.
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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by sapCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.