Bitnami package
joomla
pkg:bitnami/joomla
Vulnerabilities (144)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-26279 | Med | 6.1 | >= 3.0.0, < 5.1.2 | 5.1.2 | Jul 9, 2024 | The wrapper extensions do not correctly validate inputs, leading to XSS vectors. | |
| CVE-2024-26278 | Med | 6.1 | >= 3.7.0, < 5.1.2 | 5.1.2 | Jul 9, 2024 | The Custom Fields component not correctly filter inputs, leading to a XSS vector. | |
| CVE-2024-21731 | Med | 6.1 | >= 3.0.0, < 5.1.2 | 5.1.2 | Jul 9, 2024 | Improper handling of input could lead to an XSS vector in the StringHelper::truncate method. | |
| CVE-2024-21730 | Med | 5.4 | >= 4.0.0, < 5.1.2 | 5.1.2 | Jul 9, 2024 | The fancyselect list field layout does not correctly escape inputs, leading to a self-XSS vector. | |
| CVE-2024-21729 | Med | 6.1 | >= 4.0.0, < 5.1.2 | 5.1.2 | Jul 9, 2024 | Inadequate input validation leads to XSS vulnerabilities in the accessiblemedia field. | |
| CVE-2024-21726 | Med | 6.5 | >= 3.7.0, < 5.1.0 | 5.1.0 | Feb 29, 2024 | Inadequate content filtering leads to XSS vulnerabilities in various components. | |
| CVE-2024-21725 | Med | 6.1 | >= 4.0.0, < 5.0.3 | 5.0.3 | Feb 29, 2024 | Inadequate escaping of mail addresses lead to XSS vulnerabilities in various components. | |
| CVE-2024-21724 | Med | 6.1 | >= 1.6.0, < 5.0.3 | 5.0.3 | Feb 29, 2024 | Inadequate input validation for media selection fields lead to XSS vulnerabilities in various extensions. | |
| CVE-2024-21723 | Med | 4.3 | >= 1.5.0, < 5.0.3 | 5.0.3 | Feb 29, 2024 | Inadequate parsing of URLs could result into an open redirect. | |
| CVE-2024-21722 | Med | 6.3 | >= 3.2.0, < 5.0.3 | 5.0.3 | Feb 29, 2024 | The MFA management features did not properly terminate existing user sessions when a user's MFA methods have been modified. | |
| CVE-2023-40626 | Hig | 7.5 | >= 1.6.0, < 3.10.14 | 3.10.14 | Nov 29, 2023 | The language file parsing process could be manipulated to expose environment variables. Environment variables might contain sensible information. | |
| CVE-2023-23755 | Hig | 7.5 | >= 4.2.0, < 4.3.2 | 4.3.2 | May 30, 2023 | An issue was discovered in Joomla! 4.2.0 through 4.3.1. The lack of rate limiting allowed brute force attacks against MFA methods. | |
| CVE-2023-23754 | Med | 6.1 | >= 4.2.0, < 4.3.2 | 4.3.2 | May 30, 2023 | An issue was discovered in Joomla! 4.2.0 through 4.3.1. Lack of input validation caused an open redirect and XSS issue within the new mfa selection screen. | |
| CVE-2023-23752 | Med | 5.3 | KEV | >= 4.0.0, < 4.2.8 | 4.2.8 | Feb 16, 2023 | An issue was discovered in Joomla! 4.0.0 through 4.2.7. An improper access check allows unauthorized access to webservice endpoints. |
| CVE-2023-23751 | Med | 4.3 | >= 4.0.0, <= 4.2.4 | — | Feb 1, 2023 | An issue was discovered in Joomla! 4.0.0 through 4.2.4. A missing ACL check allows non super-admin users to access com_actionlogs. | |
| CVE-2023-23750 | Med | 6.3 | >= 4.0.0, <= 4.2.6 | — | Feb 1, 2023 | An issue was discovered in Joomla! 4.0.0 through 4.2.6. A missing token check causes a CSRF vulnerability in the handling of post-installation messages. | |
| CVE-2022-27914 | Med | 6.1 | >= 4.0.0, < 4.2.5 | 4.2.5 | Nov 8, 2022 | 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. | |
| CVE-2022-27913 | Med | 6.1 | >= 4.0.0, <= 4.2.3 | — | Oct 25, 2022 | 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. | |
| CVE-2022-27912 | Med | 5.3 | >= 4.0.0, <= 4.2.3 | — | Oct 25, 2022 | An issue was discovered in Joomla! 4.0.0 through 4.2.3. Sites with publicly enabled debug mode exposed data of previous requests. | |
| CVE-2022-27911 | Med | 5.3 | >= 4.2.0, <= 4.2.0 | — | Aug 31, 2022 | An issue was discovered in Joomla! 4.2.0. Multiple Full Path Disclosures because of missing '_JEXEC or die check' caused by the PSR12 changes. |
- affected >= 3.0.0, < 5.1.2fixed 5.1.2
The wrapper extensions do not correctly validate inputs, leading to XSS vectors.
- affected >= 3.7.0, < 5.1.2fixed 5.1.2
The Custom Fields component not correctly filter inputs, leading to a XSS vector.
- affected >= 3.0.0, < 5.1.2fixed 5.1.2
Improper handling of input could lead to an XSS vector in the StringHelper::truncate method.
- affected >= 4.0.0, < 5.1.2fixed 5.1.2
The fancyselect list field layout does not correctly escape inputs, leading to a self-XSS vector.
- affected >= 4.0.0, < 5.1.2fixed 5.1.2
Inadequate input validation leads to XSS vulnerabilities in the accessiblemedia field.
- affected >= 3.7.0, < 5.1.0fixed 5.1.0
Inadequate content filtering leads to XSS vulnerabilities in various components.
- affected >= 4.0.0, < 5.0.3fixed 5.0.3
Inadequate escaping of mail addresses lead to XSS vulnerabilities in various components.
- affected >= 1.6.0, < 5.0.3fixed 5.0.3
Inadequate input validation for media selection fields lead to XSS vulnerabilities in various extensions.
- affected >= 1.5.0, < 5.0.3fixed 5.0.3
Inadequate parsing of URLs could result into an open redirect.
- affected >= 3.2.0, < 5.0.3fixed 5.0.3
The MFA management features did not properly terminate existing user sessions when a user's MFA methods have been modified.
- affected >= 1.6.0, < 3.10.14fixed 3.10.14
The language file parsing process could be manipulated to expose environment variables. Environment variables might contain sensible information.
- affected >= 4.2.0, < 4.3.2fixed 4.3.2
An issue was discovered in Joomla! 4.2.0 through 4.3.1. The lack of rate limiting allowed brute force attacks against MFA methods.
- affected >= 4.2.0, < 4.3.2fixed 4.3.2
An issue was discovered in Joomla! 4.2.0 through 4.3.1. Lack of input validation caused an open redirect and XSS issue within the new mfa selection screen.
- affected >= 4.0.0, < 4.2.8fixed 4.2.8
An issue was discovered in Joomla! 4.0.0 through 4.2.7. An improper access check allows unauthorized access to webservice endpoints.
- affected >= 4.0.0, <= 4.2.4
An issue was discovered in Joomla! 4.0.0 through 4.2.4. A missing ACL check allows non super-admin users to access com_actionlogs.
- affected >= 4.0.0, <= 4.2.6
An issue was discovered in Joomla! 4.0.0 through 4.2.6. A missing token check causes a CSRF vulnerability in the handling of post-installation messages.
- affected >= 4.0.0, < 4.2.5fixed 4.2.5
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.
- affected >= 4.0.0, <= 4.2.3
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.
- affected >= 4.0.0, <= 4.2.3
An issue was discovered in Joomla! 4.0.0 through 4.2.3. Sites with publicly enabled debug mode exposed data of previous requests.
- affected >= 4.2.0, <= 4.2.0
An issue was discovered in Joomla! 4.2.0. Multiple Full Path Disclosures because of missing '_JEXEC or die check' caused by the PSR12 changes.
Page 4 of 8