CVE-2025-6735: A vulnerability classified as critical has been found in juzaweb CMS 3.4.2

Routine

MEDIUM 6.3DOWNGRADE

CVE-2025-6735 is a medium-severity flaw (CVSS 6.3) affecting cms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-266, CWE-285
Published	2025-06-27
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: juzaweb

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-27 00:15 UTCPublished CVE record published
2026-06-17 10:02 UTCUpdated Record last modified

juzaweb cms DOWNGRADE

Affected: 3.4.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.4.2

1. Check installed version

apt-cache policy cms || rpm -q cms || cms --version

2. No fixed release: DOWNGRADE to a release before 3.4.2 (Debian / Ubuntu)

apt-cache madison cms sudo apt install cms=<VERSION_BEFORE_3.4.2> sudo apt-mark hold cms

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list cms sudo dnf downgrade cms-<VERSION_BEFORE_3.4.2> sudo dnf versionlock add cms

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-6735?

cms: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-6735 being exploited?

CVE-2025-6735 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-6735 affect?

CVE-2025-6735 affects cms. Severity is medium (CVSS 6.3). 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 laun

How urgent is CVE-2025-6735?

Priority 38/100. Public exploit reference

Related CVEs

CVE-2025-67443 MEDIUM 6.1 UPGRADE Schlix CMS before v2.2.9-5 is vulnerable to Cross Site Scripting (XSS)
CVE-2025-6736 MEDIUM 6.3 DOWNGRADE A vulnerability classified as critical was found in juzaweb CMS 3.4.2
CVE-2025-5429 MEDIUM 6.3 UPGRADE A vulnerability classified as critical was found in juzaweb CMS up to 3.4.2
CVE-2025-5428 MEDIUM 6.3 UPGRADE A vulnerability classified as critical has been found in juzaweb CMS up to 3.4.2
CVE-2025-5427 MEDIUM 6.3 UPGRADE A vulnerability was found in juzaweb CMS up to 3.4.2

References

← Back to latest CVEs