An issue was discovered in Joomla!

published 2020-03-16 6y ago modified 2026-09-08 2mo ago also BIT-joomla-2020-10241 , EUVD-2020-2696

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

An issue was discovered in Joomla! before 3.9.16. Missing token checks in the image actions of com_templates lead to CSRF.

Patch / fix

fixed in 2

bitnami joomla 3.9.16
joomla joomla! 3.9.16

Is CVE-2020-10241 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.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
OSV	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
bitnami	joomla	>=3.2.0, <3.9.16	3.9.16

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

developer.joomla.org /security-centre/802-20200301-core-csrf-in-com-templates-image-actions
vendor-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2020-10241
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.