See how joomla compares to other vendors in security performance
Joomla! Core - [20260802] - Improper CORS origin validation in Joomla 4.0.0-5.4.7, 6.0.0-6.1.2 - An improper implementation prevented configured CORS origins from being properly validated in CORS requests.
Joomla! Core - [20260804] - Improper ACL checks for custom fields webservice endpoints in Joomla 4.0.0-5.4.7, 6.0.0-6.1.2 - An improper access check allows unauthorized users to create fields for inaccessible components.
Joomla! Core - [20260806] - XSS through schema.org outputs in Joomla 5.1.0-5.4.7, 6.0.0-6.1.2 - Improper escaping flags lead to an XSS vector in schema.org markup outputs.
Joomla! Core - [20260806] - Improper ACL checks for category webservice endpoints in Joomla 4.0.0-5.4.7, 6.0.0-6.1.2 - An improper access check allows unauthorized users to create categories via webservices endpoints.
Lack of escaping leads to an XSS vulnerability in the update list view of cominstaller.
An improper access check allows privileged users to overwrite media files without editing permissions.
An improper access check allows unauthorized users to create custom fields via webservices endpoints.
Lack of escaping leads to an XSS vulnerability in the file management view of comtemplates.
An improper access check allows unauthorized users to access workflow stage and transition information.
An improper access check allows users to display a list of modules in the frontend.
An improper access check allows unauthorized users to access comprivacy datasets.
Lack of escaping leads to XSS vulnerabilities in modalreturn layouts of various components.
Lack of escaping leads to an XSS vulnerability in the generic image output layout.
An improper access check allows user to download vcard exports of comcontact contacts that are inaccessible.
Lack of validation leads to an XSS vulnerability in the MFA management views.
Improper validation leads to a generic XSS vector in the language override feature.
The K2 frontend item.checkin task accepts an unauthenticated sigProFolder query parameter and uses it directly to address a JFolder::delete() call under /media/k2/galleries/
The K2 frontend article-attachment upload path accepts files whose extension is .php, and Apache's standard modphp matches \.php$ and executes them under the K2 web user. A K2 Author can upload a shell.php, then fetch /media/k2/attachments/shell.php and execute arbitrary PHP code in the web server's context.
The K2 frontend article-save handler accepts an attachment[N][existing] POST field that is concatenated with JPATHSITE/ and passed to JFile::copy(). JPath::clean does NOT strip .., and there is no allow-list of source paths. An Author can therefore copy configuration.php (or any other file readable by the web user — including ../../../etc/passwd) into /media/k2/attachments/, then retrieve the contents via the K2 attachment-download endpoint.
K2 ≤ 2.24 contains a mass-assignment defect in the K2 system user plugin plguserk2. A Registered Joomla user, by including the field K2UserForm=1 in a standard comusers profile.save POST, can write arbitrary values into the notes, image, and plugins columns of their own row in the #k2users table — none of which are exposed by the K2 frontend profile-edit form.
Joomla! Component Easy Shop 1.2.3 contains a local file inclusion vulnerability that allows unauthenticated attackers to read arbitrary files by supplying base64-encoded file paths. Attackers can send GET requests to index.php with the option parameter set to comeasyshop, task set to ajax.loadImage, and a base64-encoded file path in the file parameter to retrieve sensitive files like configuration.php and system files.
Improperly built filter clauses lead to a SQL injection vulnerability in the search query for comfinder.
Inadequate content filtering within the checkAttribute methods leads to XSS vulnerabilities in various components.
Lack of CSRF token validation lead to a CSRF attack vector in the admin activation endpoint of comusers.
Improperly validated order clauses lead to a SQL injection vulnerability in comtags.
An improper validation of the search parameter of the commedia files API endpoint leads to a path traversal vulnerability.
Lack of input filtering leads to an XSS vector in the HTML filter code.
Lack of output escaping leads to a XSS vector in the multilingual associations component.
An improper access check allows privilege escalation through the comusers batch task.
An improper access check allowed low privileged users to edit the task types of existing scheduler tasks.