Skip to main content
VulnerabilityPublished

CVE-2025-6736: juzaweb CMS · Improper Authorization

Affects juzaweb CMSSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% 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:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubjuzaweb/cmspkg:github/juzaweb/cmsOther threatsAffected
  • =3.4.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should include restricting access to the /admin-cp/theme/install endpoint via network-level controls such as IP whitelisting or VPN access to limit exposure to trusted administrators only. 2. Implement strict web application firewall (WAF) rules to detect and block unauthorized attempts to access or manipulate the theme installation functionality. 3. Review and harden user privilege assignments within the CMS to ensure minimal necessary permissions, reducing the risk of privilege escalation. 4. Monitor CMS logs and web server access logs for unusual activity targeting the theme installation page or attempts to bypass authorization. 5. If feasible, temporarily disable the theme installation feature until a patch or official fix is available. 6. Consider migrating to a newer, patched version of juzaweb CMS once released or evaluate alternative CMS platforms with active security support. 7. Conduct regular security assessments and penetration tests focusing on CMS administrative interfaces to detect similar authorization weaknesses. 8. Educate administrators on the risks of using outdated CMS versions and the importance of timely updates and patch management.

Description

A vulnerability classified as critical was found in juzaweb CMS 3.4.2. Affected by this vulnerability is an unknown functionality of the file /admin-cp/theme/install of the component Add New Themes Page. The manipulation leads to improper authorization. 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.

References

Community reviews

Loading reviews…