Skip to main content
VulnerabilityPublished

CVE-2025-5425: juzaweb CMS · Improper Access Controls

Affects juzaweb CMSSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 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 38% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 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.0
  • =3.4.1
  • =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. Immediately audit and restrict access to the juzaweb CMS administrative interface, especially the Theme Editor Page, limiting it to trusted personnel only.
  2. Implement strong authentication mechanisms, including multi-factor authentication (MFA), to reduce the risk of credential compromise.
  3. Monitor web server and CMS logs for unusual access patterns or unauthorized attempts to access theme editing functions.
  4. If possible, disable or restrict the /admin-cp/theme/editor/default component until a patch is available.
  5. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the theme editor paths.
  6. Regularly back up CMS configurations and themes to enable quick restoration in case of compromise.
  7. Engage with the juzaweb community or security forums for any unofficial patches or workarounds.
  8. Prepare incident response plans to address potential exploitation, including website integrity checks and forensic analysis.

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.

References

Community reviews

Loading reviews…