An issue was discovered in Joomla!

published 2020-07-15 6y ago modified 2026-09-08 2mo ago also BIT-joomla-2020-15699 , EUVD-2020-7686

cvss: 5.3; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits: 0; none known

An issue was discovered in Joomla! through 3.9.19. Missing validation checks on the usergroups table object can result in a broken site configuration.

Is CVE-2020-15699 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N
OSV	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
bitnami	joomla	>=2.5.0, <=3.9.19	no fix listed

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

developer.joomla.org /security-centre/819-20200702-core-missing-checks-can-lead-to-a-broken-usergroups-table-record.html
vendor-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2020-15699
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.