Lack of input validation in com_content leads to an open redirect.
Joomla! CMS versions 3.0.0 – 3.9.20
Upgrade to version 3.9.21
The JSST at the Joomla! Security Centre.
Lack of input validation allows com_media root paths outside of the webroot.
Joomla! CMS versions 2.5.0 – 3.9.20
Upgrade to version 3.9.21
The JSST at the Joomla! Security Centre.
Lack of escaping in mod_latestactions allows XSS attacks.
Joomla! CMS versions 3.9.0 – 3.9.20
Upgrade to version 3.9.21
The JSST at the Joomla! Security Centre.
Inadequate filtering in the system information screen could expose redis or proxy credentials
Joomla! CMS versions 3.0.0 – 3.9.19
Upgrade to version 3.9.20
The JSST at the Joomla! Security Centre.
Lack of input filtering and escaping allows XSS attacks in mod_random_image
Joomla! CMS versions 3.0.0 – 3.9.19
Upgrade to version 3.9.20
The JSST at the Joomla! Security Centre.
Internal read-only fields in the User table class could be modified by users.
Joomla! CMS versions 3.9.0 – 3.9.19
Upgrade to version 3.9.20
The JSST at the Joomla! Security Centre.
A missing token check in the remove request section of com_privacy causes a CSRF vulnerability.
Joomla! CMS versions 3.9.0 – 3.9.19
Upgrade to version 3.9.20
The JSST at the Joomla! Security Centre.
Missing validation checks at the usergroups table object can result into an broken site configuration.
Joomla! CMS versions 2.5.0 – 3.9.19
Upgrade to version 3.9.20
The JSST at the Joomla! Security Centre.
A missing token check in the ajax_install endpoint com_installer causes a CSRF vulnerability.
Joomla! CMS versions 3.7.0 – 3.9.19
Upgrade to version 3.9.20
The JSST at the Joomla! Security Centre.
Missing token checks in com_postinstall cause CSRF vulnerabilities.
Joomla! CMS versions 3.7.0 – 3.9.18
Upgrade to version 3.9.19
The JSST at the Joomla! Security Centre.
The jQuery project released version 3.5.0, and as part of that, disclosed two security vulnerabilities that affect all prior versions. As mentioned in the jQuery blog, both are “[…] security issues in jQuery’s DOM manipulation methods, as in .html(), .append(), and the others.”
The Drupal project has backported the relevant fixes back to jQuery 1.x and Joomla has adopted that patch.
Joomla! CMS versions 3.0.0 – 3.9.18
Upgrade to version 3.9.19
The JSST at the Joomla! Security Centre.
Incorrect input validation of the module tag option in com_modules allow XSS attacks.
Joomla! CMS versions 3.0.0 – 3.9.18
Upgrade to version 3.9.19
The JSST at the Joomla! Security Centre.
The default settings of the global “textfilter” configuration doesn’t block HTML inputs for ‘Guest’ users. With 3.9.19, the textfilter for new installations has been set to ‘No HTML’ for the groups ‘Public’, ‘Guest’ and ‘Registered’.
Joomla! CMS versions 2.5.0 – 3.9.18
Upgrade to version 3.9.19
The JSST at the Joomla! Security Centre.
Lack of input validation in the heading tag option of the “Articles – Newsflash” and “Articles – Categories” modules allow XSS attacks.
Joomla! CMS versions 3.0.0 – 3.9.18
Upgrade to version 3.9.19
The JSST at the Joomla! Security Centre.
Incorrect ACL checks in the access level section of com_users allow the unauthorized deletion of usergroups.
Joomla! CMS versions 2.5.0 – 3.9.16
Upgrade to version 3.9.17
The JSST at the Joomla! Security Centre.
Inproper input validations in the usergroup table class could lead to a broken ACL configuration.
Joomla! CMS versions 2.5.0 – 3.9.16
Upgrade to version 3.9.17
The JSST at the Joomla! Security Centre.
Incorrect ACL checks in the access level section of com_users allow the unauthorized editing of usergroups.
Joomla! CMS versions 3.8.8 – 3.9.16
Upgrade to version 3.9.17
The JSST at the Joomla! Security Centre.
The lack of type casting of a variable in SQL statement leads to a SQL injection vulnerability in the “Featured Articles” frontend menutype.
Joomla! CMS versions 1.7.0 – 3.9.15
Upgrade to version 3.9.16
The JSST at the Joomla! Security Centre.
Incorrect Access Control in the SQL fieldtype of com_fields allows access for non-superadmin users.
Joomla! CMS versions 3.7.0 – 3.9.15
Upgrade to version 3.9.16
The JSST at the Joomla! Security Centre.
Missing length checks in the user table can lead to the creation of users with duplicate usernames and/or email addresses.
Joomla! CMS versions 3.0.0 – 3.9.15
Upgrade to version 3.9.16
The JSST at the Joomla! Security Centre.
Various actions in com_templates lack the required ACL checks, leading to various potential attack vectors.
Joomla! CMS versions 2.5.0 – 3.9.15
Upgrade to version 3.9.16
The JSST at the Joomla! Security Centre.
Inadequate handling of CSS selectors in the Protostar and Beez3 JavaScript allow XSS attacks.
Joomla! CMS versions 3.0.0 – 3.9.15
Upgrade to version 3.9.16
The JSST at the Joomla! Security Centre.
Missing token checks in the image actions of com_templates causes CSRF vulnerabilities.
Joomla! CMS versions 3.2.0 – 3.9.15
Upgrade to version 3.9.16
The JSST at the Joomla! Security Centre.
Inadequate escaping of usernames allow XSS attacks in com_actionlogs.
Joomla! CMS versions 3.9.0 – 3.9.14
Upgrade to version 3.9.15
The JSST at the Joomla! Security Centre.
A missing CSRF token check in the LESS compiler of com_templates causes a CSRF vulnerability.
Joomla! CMS versions 3.0.0 – 3.9.14
Upgrade to version 3.9.15
The JSST at the Joomla! Security Centre.
Missing token checks in the batch actions of various components causes CSRF vulnerabilities.
Joomla! CMS versions 3.0.0 – 3.9.14
Upgrade to version 3.9.15
The JSST at the Joomla! Security Centre.
The lack of validation of configuration parameters used in SQL queries caused various SQL injection vectors.
Joomla! CMS versions 2.5.0 – 3.9.13
Upgrade to version 3.9.14
The JSST at the Joomla! Security Centre.
Missing access check in framework files could lead to a path disclosure.
Joomla! CMS versions 3.8.0 – 3.9.13
Upgrade to version 3.9.14
The JSST at the Joomla! Security Centre.
Missing access check in the phputf8 mapping files could lead to an path disclosure.
Joomla! CMS versions 3.6.0 – 3.9.12
Upgrade to version 3.9.13
The JSST at the Joomla! Security Centre.
A missing token check in com_template causes a CSRF vulnerability.
Joomla! CMS versions 3.2.0 – 3.9.12
Upgrade to version 3.9.13
The JSST at the Joomla! Security Centre.
53 queries. 9.5 mb Memory usage. 0.777 seconds.