# CVE-2025-3563: WuzhiCMS Setting index.php set code injection

> Remote attackers can inject arbitrary code via the Setting argument in WuzhiCMS, leading to potential system compromise.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2025
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-7p3g-jgfx-frjh

## What is CVE-2025-3563?

CVE-2025-3563 is a medium-severity code injection vulnerability in Wuzhicms Wuzhicms, published on 14 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in WuzhiCMS 4.1. It has been rated as critical. Affected by this issue is the function Set of the file /index.php?m=attachment&f=index&_su=wuzhicms&v=set&submit=1 of the component Setting Handler. The manipulation of the argument Setting leads to code injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Wuzhicms Wuzhicms.

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

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

## Is CVE-2025-3563 being exploited?

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

## Other vulnerabilities in Wuzhicms Wuzhicms

- [CVE-2023-52064](https://insights.sbomify.com/CVE-2023-52064/): SQL injection in n/a (critical 9.8)
- [CVE-2023-46482](https://insights.sbomify.com/CVE-2023-46482/): SQL injection in n/a (critical 9.8)
- [CVE-2020-20413](https://insights.sbomify.com/CVE-2020-20413/): SQL injection in n/a (critical 9.8)
- [CVE-2021-41654](https://insights.sbomify.com/CVE-2021-41654/): SQL injection in n/a (critical 9.8)
- [CVE-2022-27431](https://insights.sbomify.com/CVE-2022-27431/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3563 is a medium-severity code injection vulnerability in Wuzhicms Wuzhicms, published on 14 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3563 exists.

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

## Sources

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

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