CVE-2024-11972 in the critical feed json
Hunk Companion < 1.9.0 - Unauthenticated Plugin Installation
published last yr. modified 5mo ago also EUVD-2024-34370
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 59.5%
- EPSS 59.5% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 1
- Exploit-DB
Summary
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.
Patch / fix
- Unknown Hunk Companion 1.9.0
Is CVE-2024-11972 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-52259)
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
59.47% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-20).
Exploits and checks
- EDB-52259 Hunk Companion Plugin 1.9.0 - Unauthenticated Plugin Installation webapps, 2025-04-18
- wpscan.com https://wpscan.com/vulnerability/4963560b-e4ae-451d-8f94-482779c415e4/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown Hunk Companion
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/4963560b-e4ae-451d-8f94-482779c415e4/
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2024-11972
- NVD CVE-2024-11972
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.