# CVE-2025-50228: Server-side request forgery in n/a

> Attackers can exploit SSRF in Jizhicms modules to access internal resources or bypass security controls.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-3hh3-hx7r-ggc2

## What is CVE-2025-50228?

CVE-2025-50228 is a critical server-side request forgery vulnerability in n/a, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jizhicms v2.5.4 is vulnerable to Server-Side Request Forgery (SSRF) in User Evaluation, Message, and Comment modules.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Jizhicms Jizhicms.

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

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

## Is CVE-2025-50228 being exploited?

There is no known exploitation of CVE-2025-50228 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-50229](https://insights.sbomify.com/CVE-2025-50229/): SQL injection in n/a (critical 9.8)
- [CVE-2025-25784](https://insights.sbomify.com/CVE-2025-25784/): File upload in n/a (critical 9.8)
- [CVE-2024-32161](https://insights.sbomify.com/CVE-2024-32161/): File upload in n/a (critical 9.8)
- [CVE-2023-51154](https://insights.sbomify.com/CVE-2023-51154/): Path traversal in n/a (critical 9.8)
- [CVE-2021-36484](https://insights.sbomify.com/CVE-2021-36484/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50228 is a critical server-side request forgery vulnerability in n/a, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50228 in the wild and no public exploit code.

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

## Sources

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

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