Skip to main content
CVE-2024-51055VulnerabilityPublished Updated

CVE-2024-51055: Hoosk · n/a

Affects HooskSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  5. 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
GitHubhavok89/Hooskpkg:github/havok89/HooskOther threatsAffected
  • =1.7.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to the config.php component to only trusted and necessary users, enforcing the principle of least privilege. 2. Implement strict input validation and sanitization on all inputs to config.php to prevent injection of malicious scripts. 3. Monitor logs and network traffic for unusual or unauthorized access attempts targeting config.php or related components. 4. Isolate the Hoosk application environment to limit potential lateral movement if exploitation occurs. 5. Regularly review and update user privileges to ensure no excessive permissions are granted. 6. Stay alert for official patches or updates from Hoosk developers and apply them promptly once available. 7. Consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting this vulnerability. 8. Conduct security assessments or penetration tests focusing on config.php and related components to identify and remediate weaknesses.

Description

An issue Hoosk v1.7.1 allows a remote attacker to execute arbitrary code via a crafted script to the config.php component.

References

Community reviews

Loading reviews…