dbcve.org
Joomla\!Application · Joomla

CVE-2026-48948

HIGH · 8.8 CVSS v3.1 Published 2026-07-07
Fix available
A fix is available. Upgrade to 5.4.7 / 6.1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper access check allows user to download vcard exports of com_contact contacts that are inaccessible.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An improper access control vulnerability in com_contact allows authenticated users to download vcard exports of contacts they should not have access to. The application fails to properly validate user permissions before serving the vcard export, resulting in an IDOR (Insecure Direct Object Reference) that exposes restricted contact information.

MitigationImplement proper access control checks that verify user permissions before allowing vcard export downloads, ensuring users can only export contacts they are authorized to access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Joomla\!Application
Affected:>= 3.0.0, < 5.4.7>= 6.0.0, < 6.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Joomla version
    Navigate to Administrator panel > System > Information or check the libraries/cms.php file for the version number
    Affected if Version is >= 3.0.0 and < 5.4.7, OR >= 6.0.0 and < 6.1.2
  2. Verify com_contact component is present
    Check if the contact component exists in /components/com_contact/ or view it in the Administrator panel under Components > Contacts
    Affected if The com_contact component is installed and enabled in the Joomla installation
  3. Confirm vcard export functionality is available
    Navigate to a contact list view in the frontend or backend and look for a vcard export button or link, typically found in the contact listing or individual contact view
    Affected if The vcard export feature is present and accessible in the contact component
  4. Test for IDOR vulnerability in vcard export
    As an authenticated user with limited contact access, attempt to access the vcard export URL for a contact you do not have permission to view, typically via index.php?option=com_contact&task=contact.vcard&id=[CONTACT_ID]
    Affected if The vcard file downloads successfully for a contact the authenticated user should not be able to access, indicating missing permission validation

The environment is affected if Joomla version falls within the vulnerable ranges AND the vcard export can be triggered for contacts without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.4.7 / 6.1.2 or later
Fixed in 5.4.76.1.2
Interim mitigation

Implement proper access control checks that verify user permissions before allowing vcard export downloads, ensuring users can only export contacts they are authorized to access.

Recommended fix High confidence

Joomla! 5.4.7+ or Joomla! 6.1.2+ (choose the appropriate branch based on your current major version)

  1. 1. Back up your current Joomla! installation and database before attempting any upgrade.
  2. 2. Review the Joomla! upgrade documentation at docs.joomla.org for your current version path.
  3. 3. Download the appropriate patched Joomla! release (5.4.7 or later for the 5.x branch, 6.1.2 or later for the 6.x branch) from download.joomla.org.
  4. 4. For Joomla! 5.x: Extract the upgrade package and upload the files to your server, overwriting existing files while preserving your configuration.php.
  5. 5. For Joomla! 6.x: Extract the upgrade package and upload the files to your server, overwriting existing files while preserving your configuration.php.
  6. 6. Navigate to the Joomla! administrator panel and complete any database migration steps prompted during login.
  7. 7. Verify that the com_contact vCard export functionality now properly enforces access controls by testing with users who should and should not have access to contact information.
Caveat Upgrading across major Joomla! versions (e.g., 3.x to 5.x) may require template adjustments, extension compatibility verification, and database schema changes - test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Joomla\! Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48948 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data