| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| The pagination class includes arbitrary parameters in links, leading to cache poisoning attack vectors. |
| The mail template feature lacks an escaping mechanism, causing XSS vectors in multiple extensions. |
| Improper Access Controls allows backend users to overwrite their username when disallowed. |
| The stripImages and stripIframes methods didn't properly process inputs, leading to XSS vectors. |
| Various module chromes didn't properly process inputs, leading to XSS vectors. |
| Lack of output escaping in the id attribute of menu lists. |
| Improper Access Controls allows access to protected views. |
| Improper handling of identifiers lead to a SQL injection vulnerability in the quoteNameStr method of the database package. Please note: the affected method is a protected method. It has no usages in the original packages in neither the 2.x nor 3.x branch and therefore the vulnerability in question can not be exploited when using the original database class. However, classes extending the affected class might be affected, if the vulnerable method is used. |
| Insufficient state checks lead to a vector that allows to bypass 2FA checks. |
| The MFA management features did not properly terminate existing user sessions when a user's MFA methods have been modified. |
| Inadequate parsing of URLs could result into an open redirect. |
| Inadequate escaping of mail addresses lead to XSS vulnerabilities in various components. |
| Inadequate content filtering leads to XSS vulnerabilities in various components. |
| In Joomla! 1.5.0 through 3.6.5 (fixed in 3.7.0), inadequate filtering of specific HTML attributes leads to XSS vulnerabilities in various components. |
| In Joomla! before 3.8.0, a logic bug in a SQL query could lead to the disclosure of article intro texts when these articles are in the archived state. |
| In Joomla! 3.2.0 through 3.6.5 (fixed in 3.7.0), inadequate escaping of file and folder names leads to XSS vulnerabilities in the template manager component. |
| The CMS installer in Joomla! before 3.7.4 does not verify a user's ownership of a webspace, which allows remote authenticated users to gain control of the target application by leveraging Certificate Transparency logs. |
| In Joomla! before 3.8.2, a logic bug in com_fields exposed read-only information about a site's custom fields to unauthorized users. |
| In Joomla! 3.2.0 through 3.6.5 (fixed in 3.7.0), inadequate MIME type checks allowed low-privilege users to upload swf files even if they were explicitly forbidden. |
| Joomla! 3.4.4 through 3.6.3 allows attackers to reset username, password, and user group assignments and possibly perform other user account modifications via unspecified vectors. |
