# CVE-2024-30565: Code injection in n/a

> Remote attackers can execute arbitrary code via the admin notify.php endpoint in SeaCMS, requiring immediate patching.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-mcfm-cxwv-vq32

## What is CVE-2024-30565?

CVE-2024-30565 is a high-severity code injection vulnerability in Seacms Seacms, published on 4 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in SeaCMS version 12.9, allows remote attackers to execute arbitrary code via admin notify.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-30565?

It affects 1 product.


Products: Seacms Seacms.

## How do I fix CVE-2024-30565?

No fix has been published for CVE-2024-30565 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-30565 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30565 exists.

## Other vulnerabilities in Seacms Seacms

- [CVE-2025-44073](https://insights.sbomify.com/CVE-2025-44073/): SQL injection in n/a (critical 9.8)
- [CVE-2025-44071](https://insights.sbomify.com/CVE-2025-44071/): Code injection in n/a (critical 9.8)
- [CVE-2025-44072](https://insights.sbomify.com/CVE-2025-44072/): SQL injection in n/a (critical 9.8)
- [CVE-2025-44074](https://insights.sbomify.com/CVE-2025-44074/): SQL injection in n/a (critical 9.8)
- [CVE-2025-29647](https://insights.sbomify.com/CVE-2025-29647/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30565 and fix it if it is affected.

What it is: CVE-2024-30565 is a high-severity code injection vulnerability in Seacms Seacms, published on 4 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-30565 exists.

Affected product: Seacms Seacms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30565/ (Markdown: https://insights.sbomify.com/CVE-2024-30565/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30565
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30565
- OSV: https://osv.dev/vulnerability/CVE-2024-30565

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30565/
Summaries are generated and may contain mistakes; the official description above is the record.