# CVE-2025-25813: Command injection in n/a

> Attackers can execute arbitrary code remotely via the admin_files.php component in SeaCMS, requiring immediate attention from site administrators.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-q99j-qx5r-8mf7

## What is CVE-2025-25813?

CVE-2025-25813 is a medium-severity command injection vulnerability in Seacms Seacms, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component admin_files.php.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-25813?

It affects 1 product.


Products: Seacms Seacms.

## How do I fix CVE-2025-25813?

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

## Is CVE-2025-25813 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25813 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-2025-25813 and fix it if it is affected.

What it is: CVE-2025-25813 is a medium-severity command injection vulnerability in Seacms Seacms, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25813 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-2025-25813/ (Markdown: https://insights.sbomify.com/CVE-2025-25813/index.md)
```

## Sources

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

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