CVE-2025-6735VulnerabilityPublished 26 Jun 2025

CVE-2025-6735: juzaweb CMS · Improper Authorization

Affects juzaweb CMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 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

Base metrics

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

Threat metrics

Exploit Maturity: POC

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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 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 26 Oct 2026.

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.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 immediately audit their juzaweb CMS installations to identify version 3.4.2 deployments. Mitigation steps include: 1) Restricting network access to the /admin-cp/imports path by implementing IP whitelisting or VPN-only access to administrative interfaces; 2) Employing web application firewalls (WAFs) with custom rules to detect and block unauthorized requests targeting the import functionality; 3) Monitoring web server and application logs for suspicious access patterns or unauthorized attempts to reach the import page; 4) Temporarily disabling or restricting the import feature if feasible until a patch is available; 5) Conducting regular backups of CMS data and configurations to enable recovery in case of compromise; 6) Planning for an upgrade or migration to a patched or alternative CMS solution once available; 7) Engaging with juzaweb community or security forums for updates or unofficial patches; and 8) Implementing strong authentication and session management controls around the admin panel to reduce risk from other attack vectors.

Description

A vulnerability classified as critical has been found in juzaweb CMS 3.4.2. Affected is an unknown function of the file /admin-cp/imports of the component Import Page. The manipulation leads to improper authorization. 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.

Impact

For European organizations using juzaweb CMS 3.4.2, this vulnerability poses a risk of unauthorized administrative access or actions, potentially leading to data integrity issues, unauthorized content changes, or disruption of website functionality. Organizations relying on this CMS for public-facing websites or internal portals could face reputational damage, data breaches, or operational downtime if exploited. The lack of vendor response and patch availability increases the window of exposure. Since the vulnerability can be exploited remotely without authentication or user interaction, attackers can automate attacks at scale, increasing the threat level. European entities in sectors such as government, education, media, or SMEs using juzaweb CMS may be particularly vulnerable. Additionally, exploitation could serve as a foothold for further lateral movement or deployment of malware within affected networks, amplifying the impact.

Summary

CVE-2025-6735 is a medium-severity vulnerability identified in juzaweb CMS version 3.4.2, specifically within an unspecified function of the /admin-cp/imports component, known as the Import Page. The vulnerability results in improper authorization, allowing an attacker to remotely exploit the system without requiring user interaction or prior authentication. The flaw permits unauthorized access or actions that should be restricted to privileged users, potentially enabling attackers to manipulate or import data through the administrative interface. Although the exact nature of the unauthorized actions is not detailed, improper authorization in an admin context typically risks unauthorized data modification, privilege escalation, or disruption of CMS operations. The vulnerability has a CVSS 4.0 base score of 5.3, reflecting a medium impact with network attack vector, low attack complexity, no privileges required, and no user interaction needed. The vendor was notified but has not responded or provided a patch, and no known exploits have been observed in the wild yet. Given the public disclosure and availability of exploit information, the risk of exploitation may increase over time if unaddressed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jun 2025, 23:50 UTC

Technical details

References

Community reviews

Related threats