CVE-2025-5421VulnerabilityPublished 2 Jun 2025

CVE-2025-5421: 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, 07:57 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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubjuzaweb/cms`pkg:github/juzaweb/cms`Other threats	Affected =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

Given the absence of an official patch, European organizations should implement compensating controls immediately. These include restricting access to the /admin-cp/plugin/editor path via network-level controls such as IP whitelisting or VPN-only access to the administrative interface. Web Application Firewalls (WAFs) should be configured to detect and block suspicious requests targeting the plugin editor functionality. Organizations should audit user privileges to ensure minimal necessary access is granted, reducing the impact of potential exploitation. Monitoring and logging access to the administrative plugin editor page should be enhanced to detect anomalous activities promptly. Additionally, organizations should consider isolating the CMS environment and applying strict segmentation to limit potential lateral movement. Finally, organizations should maintain regular backups of CMS data and configurations to enable rapid recovery in case of compromise. Continuous monitoring for updates from the vendor or security community is essential to apply official patches once available.

Description

A vulnerability, which was classified as critical, has been found in juzaweb CMS up to 3.4.2. Affected by this issue is some unknown functionality of the file /admin-cp/plugin/editor of the component Plugin Editor Page. The manipulation leads to improper access controls. The attack may 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.

Impact

For European organizations using juzaweb CMS, this vulnerability poses a moderate risk. Exploitation could lead to unauthorized access to administrative plugin editing features, potentially allowing attackers to alter website content, inject malicious code, or disrupt website functionality. This could result in data breaches, defacement, or service interruptions, impacting brand reputation and compliance with data protection regulations such as GDPR. The medium CVSS score reflects a balance between ease of exploitation and the limited scope of impact; however, the lack of vendor response and patches increases the risk over time. Organizations with public-facing juzaweb CMS installations are particularly vulnerable, as the attack can be launched remotely without authentication. This could also facilitate further lateral movement or privilege escalation within the affected environment if combined with other vulnerabilities or misconfigurations.

Summary

CVE-2025-5421 is a vulnerability identified in the juzaweb Content Management System (CMS) versions up to 3.4.2. The issue resides in the /admin-cp/plugin/editor component, specifically within the Plugin Editor Page functionality. The vulnerability is characterized by improper access controls, allowing an attacker to bypass intended permission checks. This flaw can be exploited remotely without requiring user interaction or authentication, as indicated by the CVSS vector (AV:N/AC:L/AT:N/PR:L/UI:N). The vulnerability impacts confidentiality, integrity, and availability to a limited extent, as the CVSS score of 5.3 (medium severity) suggests. The improper access control could allow an attacker with low privileges to escalate their access or manipulate plugin editor functions, potentially leading to unauthorized modifications or exposure of sensitive administrative functions. Although the vendor was notified early, no response or patch has been issued, and no known exploits are currently reported in the wild. The vulnerability's presence in a critical administrative component makes it a significant risk for organizations relying on juzaweb CMS for website management, especially if the CMS is exposed to the internet.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 13:11 UTC

Technical details

References

Community reviews

Related threats