Skip to main content
VulnerabilityPublished

CVE-2025-5423: 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, 17:16 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 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: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

Since no official patches are available, European organizations should implement compensating controls immediately. These include restricting access to the /admin-cp/setting/system/general endpoint via network-level controls such as IP whitelisting or VPN-only access. Web application firewalls (WAFs) should be configured to detect and block suspicious requests targeting this endpoint. Organizations should audit and monitor access logs for unusual activity around the administrative interface. If possible, disable or limit the use of the affected General Setting Page until a patch is released. Regular backups of CMS configurations and content should be maintained to enable recovery in case of compromise. Additionally, organizations should consider isolating the CMS environment from other critical infrastructure to contain potential breaches. Finally, maintain vigilance for vendor updates or community patches and apply them promptly once available.

Description

A vulnerability has been found in juzaweb CMS up to 3.4.2 and classified as critical. This vulnerability affects unknown code of the file /admin-cp/setting/system/general of the component General Setting Page. The manipulation leads to improper access controls. The attack can be initiated 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…