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

> An attacker can exploit an SSRF vulnerability in MCCMS to read local files and access internal services, potentially leading to data leakage or system compromise.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-q8fh-wr43-3mgc

## What is CVE-2025-50234?

CVE-2025-50234 is a medium-severity server-side request forgery vulnerability in n/a, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MCCMS v2.7.0 has an SSRF vulnerability located in the index() method of the sys\apps\controllers\api\Gf.php file, where the pic parameter is processed. The pic parameter is decrypted using the sys_auth($pic, 1) function, which utilizes a hard-coded key Mc_Encryption_Key (bD2voYwPpNuJ7B8), defined in the db.php file. The decrypted URL is passed to the geturl() method, which uses cURL to make a request to the URL without proper security checks. An attacker can craft a malicious encrypted pic parameter, which, when decrypted, points to internal addresses or local file paths (such as http://127.0.0.1 or file://). By using the file:// protocol, the attacker can access arbitrary files on the local file system (e.g., file:///etc/passwd, file:///C:/Windows/System32/drivers/etc/hosts), allowing them to read sensitive configuration files, log files, and more, leading to information leakage or system exposure. The danger of this SSRF vulnerability includes accessing internal services and local file systems through protocols like http://, ftp://, and file://, which can result in sensitive data leakage, remote code execution, privilege escalation, or full system compromise, severely affecting the system's security and stability.

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

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

It affects 1 product.


Products: Chshcms Mccms.

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

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

## Is CVE-2025-50234 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-26781](https://insights.sbomify.com/CVE-2023-26781/): SQL injection in n/a (critical 9.8)
- [CVE-2023-29815](https://insights.sbomify.com/CVE-2023-29815/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2023-26782](https://insights.sbomify.com/CVE-2023-26782/): Code injection in n/a (medium 6.5)
- [CVE-2023-3235](https://insights.sbomify.com/CVE-2023-3235/): mccms Comic.php pic_api server-side request forgery (medium 6.3)
- [CVE-2023-3236](https://insights.sbomify.com/CVE-2023-3236/): mccms Comic.php pic_save server-side request forgery (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50234 is a medium-severity server-side request forgery vulnerability in n/a, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50234 exists.

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

## Sources

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

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