# CVE-2025-4256: SeaCMS admin_paylog.php cross site scripting

> Remote attackers can inject malicious scripts via the cstatus parameter in SeaCMS admin_paylog.php, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 May 2025
- **Updated:** 5 May 2025
- **Also known as:** GHSA-2pmm-6ghp-fx68

## What is CVE-2025-4256?

CVE-2025-4256 is a medium-severity cross-site scripting vulnerability in Seacms Seacms, published on 5 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic was found in SeaCMS 13.2. This vulnerability affects unknown code of the file /admin_paylog.php. The manipulation of the argument cstatus leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Seacms Seacms.

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

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

## Is CVE-2025-4256 being exploited?

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

What it is: CVE-2025-4256 is a medium-severity cross-site scripting vulnerability in Seacms Seacms, published on 5 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4256 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-4256/ (Markdown: https://insights.sbomify.com/CVE-2025-4256/index.md)
```

## Sources

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

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