CVE-2020-15239

LOWNVD 3.53.5—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.5 under NVD CVSS v3. EPSS exploit probability: 1.5%, top 29% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
3.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 3.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In xmpp-http-upload before version 0.4.0, when the GET method is attacked, attackers can read files which have a .data suffix and which are accompanied by a JSON file with the .meta suffix. This can lead to Information Disclosure and in some shared-hosting scenarios also to circumvention of authentication or other limitations on the outbound (GET) traffic. For example, in a scenario where a single server has multiple instances of the application running (with separate DATA_ROOT settings), an attacker who has knowledge about the directory structure is able to read files from any other instance to which the process has read access. If instances have individual authentication (for example, HTTP authentication via a reverse proxy, source IP based filtering) or other restrictions (such as quotas), attackers may circumvent those limits in such a scenario by using the Directory Traversal to retrieve data from the other instances. If the associated XMPP server (or anyone knowing the SECRET_KEY) is malicious, they can write files outside the DATA_ROOT. The files which are written are constrained to have the .meta and the .data suffixes; the .meta file will contain the JSON with the Content-Type of the original request and the .data file will contain the payload. The issue is patched in version 0.4.0.

CVSS v3
3.5
EG Score
3.5(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity35% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
71.4%
KEV
Not listed

Published

October 6, 2020

Last Modified

November 21, 2024

References (8)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
xmpp-http-upload0.1, 0.2.0, 0.3.00.4.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:15 UTCEPSS rescore
  2. 2026-07-23 14:15 UTCEPSS rescore
  3. 2026-07-23 01:49 UTCEG score recompute
  4. 2026-07-22 22:35 UTCEG score recompute
  5. 2026-07-22 14:05 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-19 14:28 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-18 10:02 UTCEPSS rescore
  14. 2026-07-16 16:59 UTCEPSS rescore
  15. 2026-07-15 16:55 UTCEPSS rescore
  16. 2026-07-15 01:57 UTCEPSS rescore
  17. 2026-07-13 22:27 UTCEPSS rescore
  18. 2026-07-13 22:27 UTCEPSS rescore
  19. 2026-07-13 06:10 UTCEPSS rescore
  20. 2026-07-13 06:10 UTCEPSS rescore
  21. 2026-07-13 01:38 UTCOSV refresh
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-11 08:25 UTCEPSS rescore
  24. 2026-07-11 08:25 UTCEPSS rescore
  25. 2026-07-09 19:07 UTCEPSS rescore
Show 72 more
  1. 2026-07-08 15:12 UTCEPSS rescore
  2. 2026-07-07 13:43 UTCEPSS rescore
  3. 2026-07-07 13:43 UTCEPSS rescore
  4. 2026-07-06 16:25 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 02:21 UTCEPSS rescore
  7. 2026-07-06 02:21 UTCEPSS rescore
  8. 2026-07-05 02:27 UTCEPSS rescore
  9. 2026-07-04 06:29 UTCEPSS rescore
  10. 2026-07-04 06:28 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-29 14:04 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 11:20 UTCOSV refresh
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-22 14:23 UTCEPSS rescore
  25. 2026-06-22 14:23 UTCEPSS rescore
  26. 2026-06-21 14:54 UTCEPSS rescore
  27. 2026-06-21 14:54 UTCEPSS rescore
  28. 2026-06-21 01:57 UTCEPSS rescore
  29. 2026-06-21 01:57 UTCEPSS rescore
  30. 2026-06-19 19:23 UTCEPSS rescore
  31. 2026-06-18 17:50 UTCEPSS rescore
  32. 2026-06-17 17:50 UTCEPSS rescore
  33. 2026-06-16 17:50 UTCEPSS rescore
  34. 2026-06-16 17:50 UTCEPSS rescore
  35. 2026-06-15 17:46 UTCEPSS rescore
  36. 2026-06-14 23:15 UTCEPSS rescore
  37. 2026-06-13 22:58 UTCEPSS rescore
  38. 2026-06-13 22:58 UTCEPSS rescore
  39. 2026-06-12 23:10 UTCEPSS rescore
  40. 2026-06-11 13:58 UTCEPSS rescore
  41. 2026-06-10 22:16 UTCEPSS rescore
  42. 2026-06-10 22:16 UTCEPSS rescore
  43. 2026-06-10 13:20 UTCEPSS rescore
  44. 2026-06-08 14:15 UTCEPSS rescore
  45. 2026-06-08 14:15 UTCEPSS rescore
  46. 2026-06-07 15:39 UTCOSV refresh
  47. 2026-06-07 15:23 UTCEPSS rescore
  48. 2026-06-07 15:23 UTCEPSS rescore
  49. 2026-06-06 13:45 UTCEPSS rescore
  50. 2026-06-06 13:45 UTCEPSS rescore
  51. 2026-06-05 22:45 UTCEPSS rescore
  52. 2026-06-05 22:45 UTCEPSS rescore
  53. 2026-06-05 06:08 UTCEPSS rescore
  54. 2026-06-04 13:10 UTCEPSS rescore
  55. 2026-06-04 13:10 UTCEPSS rescore
  56. 2026-06-02 20:11 UTCEPSS rescore
  57. 2026-06-02 20:11 UTCEPSS rescore
  58. 2026-06-01 13:50 UTCEPSS rescore
  59. 2026-05-31 22:29 UTCEPSS rescore
  60. 2026-05-31 22:29 UTCEPSS rescore
  61. 2026-05-31 00:15 UTCEPSS rescore
  62. 2026-05-31 00:14 UTCEPSS rescore
  63. 2026-05-29 13:42 UTCEPSS rescore
  64. 2026-05-29 13:42 UTCEPSS rescore
  65. 2026-05-28 13:43 UTCEPSS rescore
  66. 2026-05-28 13:43 UTCEPSS rescore
  67. 2026-05-27 13:39 UTCEPSS rescore
  68. 2026-05-26 13:42 UTCEPSS rescore
  69. 2026-05-26 13:42 UTCEPSS rescore
  70. 2026-05-26 07:17 UTCEPSS rescore
  71. 2026-05-26 07:17 UTCEPSS rescore
  72. 2026-05-23 06:58 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-15239?
CVE-2020-15239 is a low vulnerability published on October 6, 2020. In xmpp-http-upload before version 0.4.0, when the GET method is attacked, attackers can read files which have a .data suffix and which are accompanied by a JSON file with the .meta suffix. This can lead to Information Disclosure and in some shared-hosting scenarios also to circumvention of…
When was CVE-2020-15239 disclosed?
CVE-2020-15239 was first published in the National Vulnerability Database on October 6, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-15239 actively exploited?
CVE-2020-15239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-15239?
CVE-2020-15239 has a CVSS v3 base score of 3.5 (NVD).
How do I remediate CVE-2020-15239?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-15239, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-15239

Explore →

Is Your Infrastructure Affected by CVE-2020-15239?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs