CVE-2024-28397

MEDIUMNVD 5.38.8▲
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2024-06-20. NVD baseline CVSS 5.3; sources differ by 3.5.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 5%CVSS: 5.3Exploit: NoneExposed: 0

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

An issue in the component js2py.disable_pyimport() of js2py up to v0.74 allows attackers to execute arbitrary code via a crafted API call.

CVSS v3
5.3
EG Score
8.8(medium)
EPSS
90.5%
KEV
Not listed

Published

June 20, 2024

Last Modified

April 15, 2026

References (4)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipjs2py—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
js2py0.1 ... 0.74 (48 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 48× 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.

Showing the most recent 100 of 102 total refreshes for this CVE.

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

Publicly available exploits

(8 references)

Working exploit code is in the public domain (1 Metasploit module) (5 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52532
    First seen Apr 30, 2026

    Js2Py 0.74 - RCE

    Open source ↗
  • GitHub PoCxeloxa/CVE-2024-28397-Js2Py-RCE-Exploit
    First seen Feb 3, 2026

    Professional exploit for CVE-2024-28397: Js2Py Sandbox Escape leading to Remote Code Execution (RCE). Includes modular payload generation.

    Open source ↗
  • GitHub PoCL1337Xi/CVE-2024-28397-Exploit-Automation
    First seen Dec 6, 2025

    A Python automation script for exploiting the **js2py Sandbox Escape** vulnerability (CVE-2024-28397). This tool automates the payload generation and delivery process to achieve Remote Code Execution (RCE) on vulnerable instances.

    Open source ↗
  • GitHub PoCnaclapor/CVE-2024-28397
    First seen Sep 9, 2025

    This repository contains a python exploit code for CVE-2024-28397 intended for use on the "CodePartTwo" machine on Hack The Box (HTB).

    Open source ↗
  • GitHub PoCGhostOverflow/CVE-2024-28397-command-execution-poc
    First seen Aug 17, 2025

    This vulnerability arises from incomplete sandboxing in js2py, where crafted JavaScript can traverse Python’s internal object model and access dangerous classes like subprocess.Popen, leading to arbitrary command execution.

    Open source ↗
  • Metasploitexploit/linux/http/pyload_js2py_cve_2024_39205✓ verified
    First seen Oct 28, 2024

    Pyload RCE (CVE-2024-39205) with js2py sandbox escape (CVE-2024-28397)

    Open source ↗
  • GitHub PoCMarven11/CVE-2024-28397-js2py-Sandbox-Escape
    First seen Jun 19, 2024

    CVE-2024-28397: js2py sandbox escape, bypass pyimport restriction.

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-28397.yaml
    First seen Jan 1, 2024

    pyload-ng js2py - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-28397?
CVE-2024-28397 is a medium vulnerability published on June 20, 2024. An issue in the component js2py.disable_pyimport() of js2py up to v0.74 allows attackers to execute arbitrary code via a crafted API call.
When was CVE-2024-28397 disclosed?
CVE-2024-28397 was first published in the National Vulnerability Database on June 20, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-28397 actively exploited?
CVE-2024-28397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-28397?
CVE-2024-28397 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.8.
How do I remediate CVE-2024-28397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-28397, 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-2024-28397

Explore →

Is Your Infrastructure Affected by CVE-2024-28397?

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

Start Free Scan →Browse All CVEs