dbcve.org
Joomla\!Application · Joomla

CVE-2026-48956

MEDIUM · 5.0 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 →
56/100
Remediation priority · Elevated
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 users to display a list of modules in the frontend.

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 · low confidence

This is an access control vulnerability where improper authorization checks allow unauthorized users to view a list of modules in the frontend. The lack of proper access validation permits information disclosure of module listings to users who should not have that visibility.

MitigationImplement proper server-side authorization checks to verify user permissions before returning module lists. Restrict frontend module listings to only users with appropriate access rights.

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:>= 4.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
Changed
Confidentiality
Low
Integrity
None
Availability
None

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

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. Check your Joomla version
    Log into the Joomla Administrator dashboard and look at the bottom-right corner of the control panel for the version number, or check the file /libraries/src/Version.php for the VERSION constant
    Affected if The installed version falls within >= 4.0.0, < 5.4.7 or >= 6.0.0, < 6.1.2
  2. Identify the frontend module listing endpoint
    Review your web server logs or access logs for requests to /index.php?option=com_modules or similar frontend module listing URLs that may expose module data
    Affected if Requests to module listing endpoints are accessible without authentication or to low-privilege users
  3. Test unauthenticated module access
    Attempt to access the frontend module listing API or view by making a request without valid user credentials or with a low-privilege user account
    Affected if Module listings are returned to users without proper authorization checks
  4. Verify access control configuration
    Check the Joomla global configuration under System > Global Configuration > Permissions tab, and verify that the module list permission for Public or Guest user groups is set to Denied or Inherited for the frontend
    Affected if Public or Guest user groups have Allowed permission for viewing module listings in frontend permissions

You are affected if your Joomla version is 4.0.0 through 5.4.6 or 6.0.0 through 6.1.1 AND the frontend module listing is accessible to unauthorized or low-privilege users.

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 server-side authorization checks to verify user permissions before returning module lists. Restrict frontend module listings to only users with appropriate access rights.

Recommended fix High confidence

Joomla! 5.4.7 (for 5.x branch) or Joomla! 6.1.2 (for 6.x branch)

  1. 1. Identify your current Joomla! version in the administrator backend (System > Information or Dashboard)
  2. 2. If running Joomla! 5.x: plan upgrade to version 5.4.7 or later
  3. 3. If running Joomla! 6.x: plan upgrade to version 6.1.2 or later
  4. 4. Create a full backup of the Joomla! site (database and files)
  5. 5. Test the upgrade in a staging environment first
  6. 6. Apply the upgrade through Joomla! update component or manual package upload
  7. 7. Verify the upgrade was successful and access controls are enforced
Caveat Joomla! minor version upgrades typically have minimal breaking changes; verify third-party extensions are compatible before production upgrade

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-48956 — 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-48956 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