Joomla! Project Joomla! CMS vulnerabilities, page 3

137 vulnerabilities

Known vulnerabilities in Joomla! Project Joomla! CMS, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

6.1CVE-2022-27914joomla! projectjoomla! cms+1
EPSS score
0.50%
An issue was discovered in Joomla! 4.0.0 through 4.2.4. Inadequate filtering of potentially malicious user input leads to reflected XSS vulnerabilities in com_media.
6.1CVE-2022-27913joomla! projectjoomla! cms+1
EPSS score
0.44%
An issue was discovered in Joomla! 4.2.0 through 4.2.3. Inadequate filtering of potentially malicious user input leads to reflected XSS vulnerabilities in various components.
9.8CVE-2022-23797joomla! projectjoomla! cms+1
EPSS score
1.11%
An issue was discovered in Joomla! 3.0.0 through 3.10.6 & 4.0.0 through 4.1.0. Inadequate filtering on the selected Ids on an request could resulted into an possible SQL injection.
6.1CVE-2022-23800joomla! projectjoomla! cms+2
EPSS score
0.67%
An issue was discovered in Joomla! 4.0.0 through 4.1.0. Inadequate content filtering leads to XSS vulnerabilities in various components.
6.1CVE-2022-23801joomla! projectjoomla! cms+1
EPSS score
0.59%
An issue was discovered in Joomla! 4.0.0 through 4.1.0. Possible XSS atack vector through SVG embedding in com_media.
6.1CVE-2022-23798joomla! projectjoomla! cms+1
EPSS score
0.59%
An issue was discovered in Joomla! 2.5.0 through 3.10.6 & 4.0.0 through 4.1.0. Inadequate validation of URLs could result into an invalid check whether an redirect URL is internal or not.
9.8CVE-2022-23795joomla! projectjoomla! cms+1
EPSS score
1.15%
An issue was discovered in Joomla! 2.5.0 through 3.10.6 & 4.0.0 through 4.1.0. A user row was not bound to a specific authentication mechanism which could under very special circumstances allow an account takeover.
6.1CVE-2022-23796joomla! projectjoomla! cms+1
EPSS score
0.59%
An issue was discovered in Joomla! 3.7.0 through 3.10.6. Lack of input validation could allow an XSS attack using com_fields.
7.5CVE-2022-23793joomla! projectjoomla! cms+2
EPSS score
2.08%
An issue was discovered in Joomla! 3.0.0 through 3.10.6 & 4.0.0 through 4.1.0. Extracting an specifilcy crafted tar package could write files outside of the intended path.
9.8CVE-2022-23799joomla! projectjoomla! cms+2
EPSS score
1.23%
An issue was discovered in Joomla! 4.0.0 through 4.1.0. Under specific circumstances, JInput pollutes method-specific input bags with $_REQUEST data.
5.3CVE-2022-23794joomla! projectjoomla! cms+2
EPSS score
0.92%
An issue was discovered in Joomla! 3.0.0 through 3.10.6 & 4.0.0 through 4.1.0. Uploading a file name of an excess length causes the error. This error brings up the screen with the path of the source code of the web application.
6.1CVE-2024-21731joomla! projectjoomla! cms+1
EPSS score
0.44%
Improper handling of input could lead to an XSS vector in the StringHelper::truncate method.
6.3CVE-2024-21722joomla! projectjoomla! cms+1
EPSS score
0.51%
The MFA management features did not properly terminate existing user sessions when a user's MFA methods have been modified.
6.5CVE-2024-21726joomla! projectjoomla! cms+1
EPSS score
48.84%
Inadequate content filtering leads to XSS vulnerabilities in various components.
6.1CVE-2024-21724joomla! projectjoomla! cms+1
EPSS score
0.51%
Inadequate input validation for media selection fields lead to XSS vulnerabilities in various extensions.
6.1CVE-2024-21729joomla! projectjoomla! cms+1
EPSS score
0.44%
Inadequate input validation leads to XSS vulnerabilities in the accessiblemedia field.
6.1CVE-2024-21725joomla! projectjoomla! cms+1
EPSS score
32.21%
Inadequate escaping of mail addresses lead to XSS vulnerabilities in various components.
4.3CVE-2024-21723joomla! projectjoomla! cms+1
EPSS score
0.54%
Inadequate parsing of URLs could result into an open redirect.
5.4CVE-2024-21730joomla! projectjoomla! cms+1
EPSS score
0.42%
The fancyselect list field layout does not correctly escape inputs, leading to a self-XSS vector.
6.1CVE-2024-40747joomla! projectjoomla! cms+1
EPSS score
0.26%
Various module chromes didn't properly process inputs, leading to XSS vectors.