CVE-2024-53677

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 93% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
CISA-KEV: Not listedEPSS: 78%CVSS: 9.8Exploit: NoneExposed: 0

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

File upload logic in Apache Struts is flawed. An attacker can manipulate file upload params to enable paths traversal and under some circumstances this can lead to uploading a malicious file which can be used to perform Remote Code Execution.

This issue affects Apache Struts: from 2.0.0 before 6.4.0.

Users are recommended to upgrade to version 6.4.0 at least and migrate to the new file upload mechanism https://struts.apache.org/core-developers/file-upload . If you are not using an old file upload logic based on FileuploadInterceptor your application is safe.

You can find more details in  https://cwiki.apache.org/confluence/display/WW/S2-067

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.5%
KEV
Not listed

Published

December 11, 2024

Last Modified

July 15, 2025

Advisory Details (2)

Auto-updated May 26, 2026
No patch confirmed yet.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20250103-0005/
generic

S2-067 - Apache Struts 2 Wiki - Apache Software Foundation

https://cwiki.apache.org/confluence/display/WW/S2-067

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.struts:struts2-core2.0.11 ... 6.3.0.2 (96 versions)6.4.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 21× 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-22 14:07 UTCEPSS rescore
  2. 2026-07-21 15:23 UTCEPSS rescore
  3. 2026-07-19 02:28 UTCEPSS rescore
  4. 2026-07-19 02:28 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-13 22:29 UTCEPSS rescore
  7. 2026-07-13 16:38 UTCOSV refresh
  8. 2026-07-12 05:45 UTCEPSS rescore
  9. 2026-07-08 15:14 UTCEPSS rescore
  10. 2026-07-05 02:29 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-04 06:30 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-25 14:16 UTCOSV refresh
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:04 UTCEPSS rescore
  20. 2026-06-24 14:04 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-17 17:52 UTCEPSS rescore
Show 21 more
  1. 2026-06-15 17:48 UTCEPSS rescore
  2. 2026-06-13 22:59 UTCEPSS rescore
  3. 2026-06-13 22:59 UTCEPSS rescore
  4. 2026-06-12 23:11 UTCEPSS rescore
  5. 2026-06-12 23:11 UTCEPSS rescore
  6. 2026-06-08 04:28 UTCOSV refresh
  7. 2026-06-06 13:46 UTCEPSS rescore
  8. 2026-06-06 13:46 UTCEPSS rescore
  9. 2026-06-02 20:12 UTCEPSS rescore
  10. 2026-06-02 20:12 UTCEPSS rescore
  11. 2026-06-01 13:51 UTCEPSS rescore
  12. 2026-06-01 13:51 UTCEPSS rescore
  13. 2026-06-01 13:51 UTCEPSS rescore
  14. 2026-05-31 00:16 UTCEPSS rescore
  15. 2026-05-31 00:16 UTCEPSS rescore
  16. 2026-05-26 13:43 UTCEPSS rescore
  17. 2026-05-26 13:43 UTCEPSS rescore
  18. 2026-05-26 07:18 UTCEPSS rescore
  19. 2026-05-26 07:18 UTCEPSS rescore
  20. 2026-05-26 07:18 UTCEPSS rescore
  21. 2026-05-23 16:37 UTCEG score recompute

Publicly available exploits

(8 references)

Working exploit code is in the public domain (8 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCr007sec/CVE-2024-53677
    First seen Jun 3, 2025
    Open source ↗
  • GitHub PoCshishirghimir/CVE-2024-53677-Exploit
    First seen Feb 24, 2025
    Open source ↗
  • GitHub PoCSeanRickerd/CVE-2024-53677
    First seen Jan 10, 2025

    Vulnerable Environment and Exploit for CVE-2024-53677

    Open source ↗
  • GitHub PoCdustblessnotdust/CVE-2024-53677-S2-067-thread
    First seen Dec 18, 2024
    Open source ↗
  • GitHub PoCc4oocO/CVE-2024-53677-Docker
    First seen Dec 17, 2024

    A Docker-based environment to reproduce the CVE-2024-53677 vulnerability in Apache Struts 2.

    Open source ↗
  • GitHub PoCyangyanglo/CVE-2024-53677
    First seen Dec 17, 2024
    Open source ↗
  • GitHub PoCTAM-K592/CVE-2024-53677-S2-067
    First seen Dec 13, 2024

    A critical vulnerability, CVE-2024-53677, has been identified in the popular Apache Struts framework, potentially allowing attackers to execute arbitrary code remotely. This vulnerability arises from flaws in the file upload logic, which can be exploited to perform path traversal and malicious file uploads.

    Open source ↗
  • GitHub PoCcloudwafs/s2-067-CVE-2024-53677
    First seen Dec 12, 2024

    s2-067(CVE-2024-53677)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-53677?
CVE-2024-53677 is a critical vulnerability published on December 11, 2024. File upload logic in Apache Struts is flawed. An attacker can manipulate file upload params to enable paths traversal and under some circumstances this can lead to uploading a malicious file which can be used to perform Remote Code Execution. This issue affects Apache Struts: from 2.0.0 before…
When was CVE-2024-53677 disclosed?
CVE-2024-53677 was first published in the National Vulnerability Database on December 11, 2024, with the most recent update on July 15, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-53677 actively exploited?
CVE-2024-53677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-53677?
CVE-2024-53677 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-53677?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-53677, 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-53677

Explore →

Is Your Infrastructure Affected by CVE-2024-53677?

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

Start Free Scan →Browse All CVEs