Skip to main content
CVE-2024-55461VulnerabilityPublished Updated

CVE-2024-55461: sea · n/a

Affects seaSource CVE Database V5

0

Not known to be exploited · 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
1.1% chance of exploitation in 30 days – higher than 66% 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 18 Dec 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
GitHubfengfu01/seapkg:github/fengfu01/seaOther threatsAffected
  • <=13.0
Fixed in–

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

AI-suggested

To mitigate CVE-2024-55461, organizations should immediately restrict access to the phome.php file, ideally limiting it to trusted IP addresses or internal networks only. Deploy web application firewalls (WAFs) with updated rules to detect and block command injection attempts targeting the Ebak_RepPathFiletext() function or suspicious payloads in HTTP requests. Monitor server and application logs for unusual command execution patterns or unexpected system calls. If possible, disable or remove the vulnerable function or script until an official patch is released. Conduct thorough security audits of SeaCMS installations to identify and isolate vulnerable instances. Employ network segmentation to limit the impact of a potential compromise. Regularly back up critical data and verify restoration procedures to minimize damage from potential exploitation. Stay informed about vendor updates or community patches and apply them promptly once available. Additionally, consider deploying intrusion detection systems (IDS) that can detect exploitation attempts based on known signatures or anomalous behavior.

Description

SeaCMS <=13.0 is vulnerable to command execution in phome.php via the function Ebak_RepPathFiletext().

References

Community reviews

Loading reviews…