CVE-2025-5422: A vulnerability, which was classified as problematic, was found in juzaweb CMS up to 3.4.2

Routine

MEDIUM 4.3UPGRADE

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

A vulnerability, which was classified as problematic, was found in juzaweb CMS up to 3.4.2. This affects an unknown part of the file /admin-cp/logs/email of the component Email Logs Page. The manipulation leads to improper access controls. It is possible to initiate 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

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 60%)
CISA exploited list	No
Weakness	CWE-266, CWE-284
Published	2025-06-02
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-02 01:15 UTCPublished CVE record published
2026-06-17 09:47 UTCUpdated Record last modified

juzaweb cms UPGRADE

Affected: >= 3.4 and <= 3.4.2

Fixed in: newer than 3.4.2

Safe to downgrade to: a release before 3.4

1. Check installed version

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

2. UPGRADE to newer than 3.4.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.4 (Debian / Ubuntu)

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

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list cms sudo dnf downgrade cms-<VERSION_BEFORE_3.4> 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-5422?

cms: upgrade to newer than 3.4.2. Exact commands for each OS are on this page.

Is CVE-2025-5422 being exploited?

CVE-2025-5422 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-5422 affect?

CVE-2025-5422 affects cms. Severity is medium (CVSS 4.3). A vulnerability, which was classified as problematic, was found in juzaweb CMS up to 3.4.2. This affects an unknown part of the file /admin-cp/logs/email of the component Email Logs Page. The manipulation leads to improper access controls.

How urgent is CVE-2025-5422?

Priority 30/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-6735 MEDIUM 6.3 DOWNGRADE A vulnerability classified as critical has been 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

References

← Back to latest CVEs