CVE-2019-6447

The ES File Explorer File Manager application through 4.1.9.7.4 for Android allows remote attackers to read arbitrary files or execute applications via TCP port 59777 requests on the local Wi-Fi network. This TCP port remains open after the ES application has been launched once, and responds to unauthenticated application/json data over HTTP.

CVSS: 8.1High
Exploited in the wild: Not knownPublic exploit code; not in CISA KEV
EPSS: 63.8%chance of exploitation in the next 30 daystop 0.8% of scored CVEsFIRST score of 11 Nov 2026
Fix: Not stated by the vendorno fixed release in the CVE record
Published: 16 Jan 2019analysed here 12 Nov 2026

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: adjacent network
Weakness: CWE-306 Missing Authentication
Can a WAF block it?: No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

estrongs:es_file_explorer_file_manager

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. A function is missing its authentication check. The attack requests look like normal traffic, so a WAF has nothing to match on.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Not listed as of our last sync.
Public exploit code: Yes: 1 on Exploit-DB · 1 Metasploit module · 13 GitHub proofs of concept

and 9 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

9 Jan 2019First public exploit or proof of concept
16 Jan 2019Published8 days later
4 Aug 2024CVE record last updated2,027 days (about 6 years) later
12 Nov 2026Analysed by vulneraibility.com830 days (about 2 years) later

CVSS vector

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

Metric	Value	What it means
Attack vector	AdjacentSame subnet or link layer.	Same subnet or link layer.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	NoneThe service stays up.	The service stays up.

Common questions

Is CVE-2019-6447 being exploited?

Not confirmed. CVE-2019-6447 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 64% probability of exploitation in the next 30 days.

How severe is CVE-2019-6447?

CVE-2019-6447 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2019-6447?

Not known from our data. No patch reference has been recorded for CVE-2019-6447, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2019-6447 affect?

CVE-2019-6447 affects estrongs:es_file_explorer_file_manager. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

3 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
FIRST EPSS: exploit probability and percentile
Exploit-DB: published exploits
Metasploit Framework: exploit and scanner modules
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.