Threats / Apache / CVE-2019-0193
CVE-2019-0193
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apache Solr vulnerability
Apache Solr's optional DataImportHandler module contains a code injection vulnerability (CWE-94) that allows remote code execution. The flaw has been exploited in the wild.
Verdict
Today item — known-exploited.
An unauthenticated attacker can inject and execute arbitrary code through the DataImportHandler module in vulnerable Apache Solr instances. Active exploitation in the wild combined with high EPSS score indicates immediate risk to exposed deployments.
CISA KEV Yes · 2021-12-104EPSS 0.83547 (verify live)5Exploit Weaponized · public PoC6CVSS 7.2 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
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
169 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-12-10).
Probability (EPSS)
EPSS 0.83547 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) · Affected: Apache, Solr. 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-94 Code Injection — weakness family: Injection.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: 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 862 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: 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 craft a malicious request containing code injection payloads targeting the DataImportHandler endpoint.
Business
Exposed Solr instances become entry points for unauthorized code execution and system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary commands on the target system with the privileges of the Solr process.
Business
Attackers gain persistent access to infrastructure, enabling data theft, lateral movement, and operational disruption.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish command and control channels or deploy malware for sustained presence.
Business
Organizations face prolonged security incidents, compliance violations, and potential regulatory penalties.
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