dbcve.org
Joomla\!Application · Joomla

CVE-2026-48899

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 5.4.6 / 6.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 privilege escalation through the com_users batch task.

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

This is a broken access control vulnerability in Joomla's com_users component where the batch task lacks proper authorization checks, allowing authenticated users to escalate privileges by manipulating user accounts through the batch operation.

MitigationImplement proper access control validation in the com_users batch task to ensure users can only perform batch operations on accounts they are authorized to manage.

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.6>= 6.0.0, < 6.1.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 your Joomla version
    Access the Joomla administrator dashboard and navigate to System > Information > System Information, or check the libraries/joomla/version.php file for the installed version number
    Affected if The installed version is >= 4.0.0 and < 5.4.6, or >= 6.0.0 and < 6.1.1
  2. Verify com_users component access
    Log into the backend with the user account in question and attempt to access the User Manager component via index.php?option=com_users
    Affected if The user can access com_users without receiving an access denied error
  3. Confirm batch operations are available
    In the User Manager (com_users), navigate to the Users view and look for the Batch button or toolbar action that allows group assignment or permission changes across multiple users
    Affected if Batch operations are visible and functional for this user account
  4. Check user group privileges
    Examine the user's assigned group in the User Manager to determine their actual privilege level - look at whether they are in a group with Super Admin, Administrator, or lower-level permissions
    Affected if The user has limited privileges (such as Registered, Author, Editor) but can still access and use batch operations in com_users

You are affected if your Joomla version falls within the vulnerable ranges AND low-privileged authenticated users can access the com_users component batch operations to modify user groups or permissions.

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.6 / 6.1.1 or later
Fixed in 5.4.66.1.1
Interim mitigation

Implement proper access control validation in the com_users batch task to ensure users can only perform batch operations on accounts they are authorized to manage.

Recommended fix High confidence

Joomla! 5.4.6 or Joomla! 6.1.1

  1. 1. Back up your Joomla! database and all files before proceeding with any upgrade.
  2. 2. Download Joomla! 5.4.6 (if running Joomla! 5.x) or Joomla! 6.1.1 (if running Joomla! 6.x) from the official Joomla! downloads page.
  3. 3. Install the update through the Joomla! Administrator Update component, or manually upload the upgrade package.
  4. 4. After upgrade, verify the site functionality and test user management operations.
  5. 5. Review user accounts in com_users to confirm no unauthorized privilege escalation occurred.
Caveat Standard Joomla! upgrade considerations apply - review third-party extensions compatibility before upgrading

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48899 — 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-48899 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