# CVE-2019-25778: SeaCMS 8.7 SQL Injection via comment/api/index.php rlist Parameter


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-x45m-w3f3-v256

## What is CVE-2019-25778?

CVE-2019-25778 is a high-severity vulnerability in SeaCMS, published on 22 Oct 2026. 

### Official description

SeaCMS through 8.7 contains an unauthenticated SQL injection vulnerability that allows remote attackers to manipulate database queries by injecting SQL through the rlist[] array parameter. Attackers can send GET requests to /comment/api/index.php with crafted rlist[] values using backtick-quoted variables and extractvalue to extract database information via error messages. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25778?


## How do I fix CVE-2019-25778?

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

## Is CVE-2019-25778 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25778 and fix it if it is affected.

What it is: CVE-2019-25778 is a high-severity vulnerability in SeaCMS, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25778 exists.

Affected product: 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-2019-25778/ (Markdown: https://insights.sbomify.com/CVE-2019-25778/index.md)
```

## Sources

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

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