# CVE-2025-1891: shishuocms cross-site request forgery

> A cross-site request forgery vulnerability in shishuocms allows remote attackers to perform unauthorized actions on behalf of authenticated users.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Mar 2025
- **Updated:** 28 Aug 2025
- **Also known as:** GHSA-4jxh-cpm8-pf72

## What is CVE-2025-1891?

CVE-2025-1891 is a medium-severity vulnerability in shishuocms, published on 3 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in shishuocms 1.1 and classified as problematic. This issue affects some unknown processing. The manipulation leads to cross-site request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Qzw1210 Shishuocms.

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

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

## Is CVE-2025-1891 being exploited?

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

## Other vulnerabilities in shishuocms

- [CVE-2025-1892](https://insights.sbomify.com/CVE-2025-1892/): shishuocms Directory Deletion Page add.json cross site scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1891 and fix it if it is affected.

What it is: CVE-2025-1891 is a medium-severity vulnerability in shishuocms, published on 3 Mar 2025. An attacker can exploit it over the internet without logging in, 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-1891 exists.

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

## Sources

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

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