| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Joomla up to 3.10.19/4.4.9/5.2.2. The affected element is an unknown function of the component View Handler. Performing a manipulation results in access control. This vulnerability is reported as CVE-2024-40749. No exploit exists.
Details
A vulnerability classified as critical has been found in Joomla up to 3.10.19/4.4.9/5.2.2. This affects an unknown code of the component View Handler. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed by Dominik Ziegelmüller. The advisory is shared at developer.joomla.org. This vulnerability is uniquely identified as CVE-2024-40749 since 07/09/2024. The exploitability is told to be easy. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/05/2025). MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 214093 (Joomla 3.9.x < 3.10.20 / 4.0.x < 4.4.10 / 5.0.x < 5.2.3 Joomla 5.2.3 Security & Bugfix Release (5919-joomla-5-2-3-security-bugfix-release)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (214093). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 3.10.0
- 3.10.1
- 3.10.2
- 3.10.3
- 3.10.4
- 3.10.5
- 3.10.6
- 3.10.7
- 3.10.8
- 3.10.9
- 3.10.10
- 3.10.11
- 3.10.12
- 3.10.13
- 3.10.14
- 3.10.15
- 3.10.16
- 3.10.17
- 3.10.18
- 3.10.19
- 4.4.0
- 4.4.1
- 4.4.2
- 4.4.3
- 4.4.4
- 4.4.5
- 4.4.6
- 4.4.7
- 4.4.8
- 4.4.9
- 5.2.0
- 5.2.1
- 5.2.2
License
Website
- Product: https://www.joomla.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 214093
Nessus Name: Joomla 3.9.x < 3.10.20 / 4.0.x < 4.4.10 / 5.0.x < 5.2.3 Joomla 5.2.3 Security & Bugfix Release (5919-joomla-5-2-3-security-bugfix-release)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/09/2024 🔍01/07/2025 🔍
01/07/2025 🔍
06/05/2025 🔍
Sources
Product: joomla.orgAdvisory: developer.joomla.org
Researcher: Dominik Ziegelmüller
Status: Not defined
CVE: CVE-2024-40749 (🔍)
GCVE (CVE): GCVE-0-2024-40749
GCVE (VulDB): GCVE-100-290637
Entry
Created: 01/07/2025 18:00Updated: 06/05/2025 05:13
Changes: 01/07/2025 18:00 (53), 01/15/2025 05:57 (2), 06/05/2025 05:13 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.