| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Lack of output escaping leads to a XSS vector in the content history component. |
| Lack of CSRF token validation lead to a CSRF attack vector in the admin activation endpoint of com_users. |
| Insufficient state checks lead to a vector that allows to bypass 2FA checks. |
| Inadequate content filtering within the checkAttribute methods leads to XSS vulnerabilities in various components. |
| The password and username reset features created plain http links for https connections if the "Force SSL" flag wasn't explicitly set. |
| Insufficient state checks lead to a vector that allows to bypass 2FA checks. |
| The InputFilter::getInstance() method omitted a security sensitive parameter from the instance cache key. |
| An improper validation of the search parameter of the com_media files API endpoint leads to a path traversal vulnerability. |
| An improper access check allows unauthorized access to com_config webservice endpoints. |
| Lack of output escaping leads to a XSS vector in the feed modules. |
| Lack of output escaping leads to a XSS vector in the multilingual associations component. |
| Lack of output escaping leads to a XSS vector in the readmore links for com_content. |
| Improperly built filter clauses lead to a SQL injection vulnerability in the search query for com_finder. |
| An improper validation of user-supplied input leads to a local file inclusion vulnerability. |
| An improper access check allows privilege escalation through the com_users batch task. |
| An improper access check allows privelege escalation through the com_users group editing webservice endpoint. |
| An improper access check allowed low privileged users to edit the task types of existing scheduler tasks. |
| An improper access check allows privilege escalation through the com_users batch task. |
| Lack of input filtering leads to an XSS vector in the HTML filter code. |
| Joomla! 1.5.0 Beta allows remote attackers to obtain sensitive information via a direct request for (1) plugins/user/example.php; (2) gmail.php, (3) example.php, or (4) ldap.php in plugins/authentication/; (5) modules/mod_mainmenu/menu.php; or other unspecified PHP scripts, which reveals the path in various error messages, related to a jimport function call at the beginning of each script. |
