# CVE-2025-5425: juzaweb CMS Theme Editor Page default access control

> Attackers can bypass access controls in the Theme Editor to gain unauthorized privileges or execute code in juzaweb CMS.

- **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:** 2 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-h2gw-573j-3mjj

## What is CVE-2025-5425?

CVE-2025-5425 is a medium-severity missing authorization vulnerability in juzaweb CMS, published on 2 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in juzaweb CMS up to 3.4.2. It has been classified as critical. Affected is an unknown function of the file /admin-cp/theme/editor/default of the component Theme Editor Page. The manipulation leads to improper access controls. It is possible to launch the attack 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-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Juzaweb Cms.

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

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

## Is CVE-2025-5425 being exploited?

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

## Other vulnerabilities in juzaweb CMS

- [CVE-2023-46467](https://insights.sbomify.com/CVE-2023-46467/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2025-6735](https://insights.sbomify.com/CVE-2025-6735/): juzaweb CMS Import Page imports improper authorization (medium 5.3)
- [CVE-2025-6736](https://insights.sbomify.com/CVE-2025-6736/): juzaweb CMS Add New Themes Page install improper authorization (medium 5.3)
- [CVE-2025-5421](https://insights.sbomify.com/CVE-2025-5421/): juzaweb CMS Plugin Editor Page editor access control (medium 5.3)
- [CVE-2025-5422](https://insights.sbomify.com/CVE-2025-5422/): juzaweb CMS Email Logs Page email access control (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5425 is a medium-severity missing authorization vulnerability in juzaweb CMS, published on 2 Jun 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-5425 exists.

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

## Sources

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

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