Hunk Companion Plugin up to 1.8.x on WordPress REST API Endpoint authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Hunk Companion Plugin up to 1.8.x on WordPress and classified as problematic. Affected by this vulnerability is an unknown functionality of the component REST API Endpoint. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2024-11972. The attack is possible to be carried out remotely. Moreover, an exploit is present. The affected component should be upgraded.
Details
A vulnerability was found in Hunk Companion Plugin up to 1.8.x on WordPress. It has been rated as problematic. This issue affects an unknown part of the component REST API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is integrity. The summary by CVE is:
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.
The weakness was disclosed by Daniel Rodriguez. The advisory is shared at wpscan.com. The identification of this vulnerability is CVE-2024-11972 since 11/28/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 1.9.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (52259). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.3
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (WPScan): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Hunk Companion Plugin 1.9.0
Timeline
11/28/2024 🔍12/31/2024 🔍
12/31/2024 🔍
06/12/2025 🔍
Sources
Advisory: wpscan.comResearcher: Daniel Rodriguez
Status: Confirmed
CVE: CVE-2024-11972 (🔍)
GCVE (CVE): GCVE-0-2024-11972
GCVE (VulDB): GCVE-100-289817
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/31/2024 09:19Updated: 06/12/2025 02:57
Changes: 12/31/2024 09:19 (56), 12/31/2024 12:23 (1), 12/31/2024 21:03 (11), 06/12/2025 02:57 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.