Skip to main content
CVE-2024-9707VulnerabilityPublished Updated

CVE-2024-9707: Hunk Companion (WordPress plugin) · Missing Authorization

Affects Hunk Companion (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
9.0% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Oct 2024

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
themehunk Hunk CompanionAffected
  • =0
Fixed in–

AI-suggested

Until a fix is available, restrict access to the REST API endpoint if possible and monitor for suspicious plugin installations. Avoid installing or activating untrusted plugins and consider disabling the Hunk Companion plugin if feasible.

Description

The Hunk Companion plugin for WordPress is vulnerable to unauthorized plugin installation/activation due to a missing capability check on the /wp-json/hc/v1/themehunk-import REST API endpoint in all versions up to, and including, 1.8.4. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated.

References

Community reviews

Loading reviews…