# CVE-2025-2607: phplaozhang LzCMS-LaoZhangBoKeXiTong HTTP POST Request upimage.html unrestricted upload

> Attackers can upload malicious files via the admin upload handler, potentially leading to remote code execution on the LzCMS web application.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2025
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-p2r4-qh4v-qvh7

## What is CVE-2025-2607?

CVE-2025-2607 is a medium-severity vulnerability in phplaozhang LzCMS-LaoZhangBoKeXiTong, published on 21 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in phplaozhang LzCMS-LaoZhangBoKeXiTong up to 1.1.4. It has been rated as critical. Affected by this issue is some unknown functionality of the file /admin/upload/upimage.html of the component HTTP POST Request Handler. The manipulation of the argument File leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Phplaozhang Lzcms-Laozhangbokexitong.

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

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

## Is CVE-2025-2607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2607 is a medium-severity vulnerability in phplaozhang LzCMS-LaoZhangBoKeXiTong, published on 21 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2607 exists.

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

## Sources

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

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