Skip to main content
VulnerabilityPublished

CVE-2025-5429: 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, 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 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 immediate compensating controls. These include restricting access to the /admin-cp/plugin/install endpoint via network-level controls such as IP whitelisting or VPN-only access, and deploying web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting plugin installation. Regularly monitoring web server logs for unusual access patterns to the vulnerable endpoint is critical. Organizations should also consider disabling plugin installation functionality if not required or isolating the CMS environment to limit potential lateral movement. Promptly updating juzaweb CMS once a vendor patch is released is essential. Additionally, conducting internal security assessments to identify any unauthorized changes or signs of compromise related to plugin management is recommended.

Description

A vulnerability classified as critical was found in juzaweb CMS up to 3.4.2. This vulnerability affects unknown code of the file /admin-cp/plugin/install of the component Plugins 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…