CVE-2024-11972

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-12-31. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 55%
CISA-KEV: Not listedEPSS PROB: 55%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

The Hunk Companion WordPress plugin before 1.9.0 does not correctly authorize some REST API endpoints, allowing unauthenticated requests to install and activate arbitrary Hunk Companion WordPress plugin before 1.9.0 from the WordPress.org repo, including vulnerable Hunk Companion WordPress plugin before 1.9.0 that have been closed.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
81(Track)
EG Risk 81/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
Severity98% × 45%
Exploitation55% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
55%
EPSS %ILE
99%
KEV
Not listed

Published

December 31, 2024

Last Modified

May 17, 2025

Advisory Details (1)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Hunk Companion < 1.9.0 – Unauthenticated Plugin Installation | CVE 2024-11972 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/4963560b-e4ae-451d-8f94-482779c415e4/

Data Freshness Timeline

(refreshed 3× in last 7d / 29× 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-08-07 16:25 UTCEPSS rescore
  2. 2026-08-06 13:45 UTCEPSS rescore
  3. 2026-08-05 19:15 UTCEPSS rescore
  4. 2026-08-01 04:14 UTCEPSS rescore
  5. 2026-08-01 04:14 UTCEPSS rescore
  6. 2026-07-30 16:26 UTCEPSS rescore
  7. 2026-07-30 01:29 UTCEPSS rescore
  8. 2026-07-28 15:34 UTCEPSS rescore
  9. 2026-07-26 14:53 UTCEPSS rescore
  10. 2026-07-26 14:53 UTCEPSS rescore
  11. 2026-07-24 14:16 UTCEPSS rescore
  12. 2026-07-23 02:31 UTCEG score recompute
  13. 2026-07-22 23:18 UTCEG score recompute
  14. 2026-07-22 14:07 UTCEPSS rescore
  15. 2026-07-20 17:06 UTCEPSS rescore
  16. 2026-07-19 14:30 UTCEPSS rescore
  17. 2026-07-19 14:30 UTCEPSS rescore
  18. 2026-07-19 02:27 UTCEPSS rescore
  19. 2026-07-15 16:56 UTCEPSS rescore
  20. 2026-07-15 16:56 UTCEPSS rescore
  21. 2026-07-15 01:59 UTCEPSS rescore
  22. 2026-07-15 01:59 UTCEPSS rescore
  23. 2026-07-13 22:28 UTCEPSS rescore
  24. 2026-07-13 06:11 UTCEPSS rescore
  25. 2026-07-13 06:11 UTCEPSS rescore
Show 44 more
  1. 2026-07-12 05:45 UTCEPSS rescore
  2. 2026-07-12 05:45 UTCEPSS rescore
  3. 2026-07-11 08:26 UTCEPSS rescore
  4. 2026-07-09 19:09 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-05 02:29 UTCEPSS rescore
  7. 2026-07-01 15:05 UTCEPSS rescore
  8. 2026-06-30 23:21 UTCEPSS rescore
  9. 2026-06-30 23:21 UTCEPSS rescore
  10. 2026-06-29 14:05 UTCEPSS rescore
  11. 2026-06-28 14:06 UTCEPSS rescore
  12. 2026-06-28 14:06 UTCEPSS rescore
  13. 2026-06-27 03:07 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-25 13:48 UTCEPSS rescore
  16. 2026-06-23 21:32 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-21 01:58 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-17 17:52 UTCEPSS rescore
  21. 2026-06-17 17:51 UTCEPSS rescore
  22. 2026-06-16 17:51 UTCEPSS rescore
  23. 2026-06-16 17:51 UTCEPSS rescore
  24. 2026-06-15 17:47 UTCEPSS rescore
  25. 2026-06-12 23:11 UTCEPSS rescore
  26. 2026-06-12 23:11 UTCEPSS rescore
  27. 2026-06-10 22:17 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-06 13:46 UTCEPSS rescore
  32. 2026-06-06 13:46 UTCEPSS rescore
  33. 2026-06-02 20:12 UTCEPSS rescore
  34. 2026-06-02 20:12 UTCEPSS rescore
  35. 2026-06-01 13:51 UTCEPSS rescore
  36. 2026-06-01 13:51 UTCEPSS rescore
  37. 2026-05-29 13:43 UTCEPSS rescore
  38. 2026-05-28 13:44 UTCEPSS rescore
  39. 2026-05-28 13:44 UTCEPSS rescore
  40. 2026-05-28 13:44 UTCEPSS rescore
  41. 2026-05-26 13:43 UTCEPSS rescore
  42. 2026-05-26 13:43 UTCEPSS rescore
  43. 2026-05-23 14:43 UTCEG score recompute
  44. 2026-05-23 14:43 UTCGHSA enrichment

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-52259
    First seen Apr 18, 2025

    Hunk Companion Plugin 1.9.0 - Unauthenticated Plugin Installation

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

    Hunk Companion < 1.9.0 - Unauthenticated Plugin Installation

    Open source ↗

Frequently asked(5)

What is CVE-2024-11972?
CVE-2024-11972 is a critical vulnerability published on December 31, 2024. The Hunk Companion WordPress plugin before 1.9.0 does not correctly authorize some REST API endpoints, allowing unauthenticated requests to install and activate arbitrary Hunk Companion WordPress plugin before 1.9.0 from the WordPress.org repo, including vulnerable Hunk Companion WordPress plugin…
When was CVE-2024-11972 disclosed?
CVE-2024-11972 was first published in the National Vulnerability Database on December 31, 2024, with the most recent update on May 17, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-11972 actively exploited?
CVE-2024-11972 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 55% probability of exploitation in the next 30 days, which ranks it in the top 1.1% of all scored CVEs.
What is the CVSS score of CVE-2024-11972?
CVE-2024-11972 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-11972?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-11972, 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

Explore the affected products and dependency analysis for CVE-2024-11972

Explore →

Is Your Infrastructure Affected by CVE-2024-11972?

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

Start Free Scan →Browse All CVEs