Joomla! Project Joomla! CMS up to 6.1.1 com_contact access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $5k-$25k | 0.57+ |
Summary
A vulnerability was found in Joomla! Project Joomla! CMS up to 6.1.1 and classified as problematic. This impacts an unknown function of the component com_contact. Executing a manipulation can lead to access control. This vulnerability is registered as CVE-2026-48948. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as problematic was found in Joomla! Project Joomla! CMS up to 6.1.1. This vulnerability affects an unknown code of the component com_contact. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality. CVE summarizes:
An improper access check allows user to download vcard exports of com_contact contacts that are inaccessible.
The advisory is shared for download at developer.joomla.org. This vulnerability was named CVE-2026-48948 since 05/26/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 07/07/2026). The MITRE ATT&CK project declares the attack technique as T1068.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
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: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/26/2026 CVE reserved07/07/2026 Advisory disclosed
07/07/2026 VulDB entry created
07/07/2026 VulDB entry last update
Sources
Advisory: developer.joomla.orgStatus: Confirmed
CVE: CVE-2026-48948 (🔒)
GCVE (CVE): GCVE-0-2026-48948
GCVE (VulDB): GCVE-100-376660
Entry
Created: 07/07/2026 20:29Changes: 07/07/2026 20:29 (53)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.