CVE-2026-48957: An improper access check allows unauthorized users to access com_privacy datasets.

This month

HIGH 8.8UPGRADE

CVE-2026-48957 is a high-severity flaw (CVSS 8.8) affecting joomla\!. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An improper access check allows unauthorized users to access com_privacy datasets.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-284
Published	2026-07-07
Last modified	2026-10-25

Publisher (CNA): Joomla! Project · Vendor: joomla

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

Am I affected?

Timeline

2026-07-07 19:16 UTCPublished CVE record published
2026-10-25 20:10 UTCUpdated Record last modified

joomla joomla\! UPGRADE

Affected: >= 4.0.0 and < 5.4.7 · >= 6.0.0 and < 6.1.2

Fixed in: 5.4.7, 6.1.2

Safe to downgrade to: a release before 4.0.0

1. Check installed version

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

2. UPGRADE to 5.4.7 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade joomla

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 4.0.0 (Debian / Ubuntu)

apt-cache madison joomla sudo apt install joomla=<VERSION_BEFORE_4.0.0> sudo apt-mark hold joomla

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

dnf --showduplicates list joomla sudo dnf downgrade joomla-<VERSION_BEFORE_4.0.0> sudo dnf versionlock add joomla

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-2026-48957?

joomla\!: upgrade to 5.4.7, 6.1.2. Exact commands for each OS are on this page.

Is CVE-2026-48957 being exploited?

CVE-2026-48957 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-2026-48957 affect?

CVE-2026-48957 affects joomla\!. Severity is high (CVSS 8.8). An improper access check allows unauthorized users to access com_privacy datasets.

How urgent is CVE-2026-48957?

Priority 40/100. High severity

Software pages

Joomla vulnerabilities

Related CVEs

CVE-2026-48958 HIGH 8.8 UPGRADE An improper access check allows unauthorized users to create custom fields via webservices endpoints.
CVE-2026-48948 HIGH 8.8 UPGRADE An improper access check allows user to download vcard exports of com_contact contacts that are inaccessible.
CVE-2026-48955 MEDIUM 6.5 UPGRADE An improper access check allows unauthorized users to access workflow stage and transition information.
CVE-2026-48949 MEDIUM 6.1 UPGRADE Lack of validation leads to an XSS vulnerability in the MFA management views.
CVE-2026-48950 MEDIUM 6.1 UPGRADE Lack of escaping leads to an XSS vulnerability in the file management view of com_templates.

References

← Back to latest CVEs