# CVE-2023-46906: juzawebCMS Incorrect Access Control vulnerability

> Attackers can cause a denial of service in Juzaweb by sending unvalidated payloads in the timezone field, leading to application outages.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2024
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-93p6-9cxv-5rpq

## What is CVE-2023-46906?

CVE-2023-46906 is a medium-severity missing authorization vulnerability in n/a, published on 9 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

juzaweb <= 3.4 is vulnerable to Incorrect Access Control, resulting in an application outage after a 500 HTTP status code. The payload in the timezone field was not correctly validated.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-46906?

2 open source packages ship an affected version, including juzaweb/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `juzaweb/cms` | Packagist | All versions to 3.4 | None |
| `juzaweb/cms` | Packagist | All versions to 3.4 | None |

Products: Juzaweb Cms.

## How do I fix CVE-2023-46906?

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

## Is CVE-2023-46906 being exploited?

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

## Other vulnerabilities in n/a

- [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-2023-46906 and fix it if it is affected.

What it is: CVE-2023-46906 is a medium-severity missing authorization vulnerability in n/a, published on 9 Jan 2024. 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-2023-46906 exists.

Affected packages and fixed versions:
- juzaweb/cms (Packagist): affected all versions up to 3.4; no fix listed
- juzaweb/cms (Packagist): affected all versions up to 3.4; no fix listed

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

## Sources

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

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