CVE-2024-11972

Themehunk Hunk Companion vulnerability

9.8 CRITICALEPSS 59.1%

Published31 Dec 2024

Description

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 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Themehunk Hunk Companion< 1.9.0

Remediation

Fixed in

Themehunk Hunk Companion≥ 1.9.0

Frequently asked

Is CVE-2024-11972 being actively exploited?

CVE-2024-11972 is not in the CISA KEV catalog. Its EPSS exploit probability is 59.1%.

How severe is CVE-2024-11972?

CVE-2024-11972 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 59.1% probability of exploitation.

Which products are affected by CVE-2024-11972?

Affected products include Themehunk Hunk Companion.

How do I fix CVE-2024-11972?

Upgrade affected software to a fixed version, for example Themehunk Hunk Companion 1.9.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-11972 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.