CVE-2025-5426: juzaweb CMS · Improper Access Controls
Affects juzaweb CMSSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjuzaweb/cmspkg:github/juzaweb/cmsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately audit their juzaweb CMS installations to identify affected versions (3.4.0 to 3.4.2). Until an official patch is released, organizations should implement strict network-level access controls to restrict access to the /admin-cp/menus path, ideally limiting it to trusted IP addresses or VPN users. Web application firewalls (WAFs) should be configured to detect and block suspicious requests targeting the admin menu component. Administrators should monitor CMS logs for unusual access patterns or unauthorized attempts to access administrative menus. It is also advisable to enforce strong authentication and session management policies to reduce the risk of privilege escalation. Organizations should consider isolating the CMS backend from public networks where feasible. Regular backups of CMS configurations and content should be maintained to enable rapid recovery if exploitation occurs. Finally, organizations should engage with the juzaweb community or security forums to track any forthcoming patches or advisories and apply updates promptly once available.
Description
A vulnerability was found in juzaweb CMS up to 3.4.2. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /admin-cp/menus of the component Menu Page. The manipulation leads to improper access controls. The attack can 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.