Admin-triggered application outage via malformed timezone input
Published Jan 9, 2024 · Updated Apr 17, 2025
Incorrect access control in Juzaweb CMS 3.4 and earlier allows remote authenticated users to interrupt the application via timezone input. The timezone field accepts a malformed payload without adequate validation, and processing that value returns HTTP 500 and leaves the application unavailable. A high-privilege account is required; public sources do not disclose the exact authorization path or duration of the outage.
Summary
What happened
Incorrect access control in Juzaweb CMS 3.4 and earlier allows remote authenticated users to interrupt the application via timezone input. The timezone field accepts a malformed payload without adequate validation, and processing that value returns HTTP 500 and leaves the application unavailable. A high-privilege account is required; public sources do not disclose the exact authorization path or duration of the outage.
The record
- CVE
- CVE-2023-46906
- Published
- Jan 9, 2024
- Updated
- Apr 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1499.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Apr 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Timezone-field outage proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo