dbcve.org
Joomla\!Application · Joomla

CVE-2026-48955

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-07
Fix available
A fix is available. Upgrade to 6.1.2 or later.
See remediation →
71/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 unauthorized users to access workflow stage and transition information.

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 where the application fails to properly validate user permissions before allowing access to workflow stage and transition data. An authenticated but unauthorized user can view sensitive workflow information they should not have access to.

MitigationImplement and enforce proper authorization checks at all entry points to workflow stage and transition data, ensuring users can only access information for workflows they are explicitly permitted to view.

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:>= 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify installed Joomla version
    Access the Joomla administrator backend and navigate to System > Information > Joomla Information, or check the libraries/joomla/version.php file for the installed version number
    Affected if The installed version is >= 6.0.0 and < 6.1.2
  2. Verify workflow component is in use
    Check if the Joomla workflow component (com_workflow) is installed and enabled by navigating to Components > Workflows in the administrator panel, or inspect the #__extensions table for the workflow component entry
    Affected if The workflow component is installed and enabled on the site
  3. Confirm user access control configuration
    Review the permissions assigned to user groups for the workflow component by going to Users > Access Levels in the administrator backend, and verify which user groups have access to workflow stage and transition viewing
    Affected if Any authenticated user group has permission to view workflow stages or transitions without proper workflow-specific authorization checks
  4. Test for unauthorized workflow data exposure
    Create a test user account with limited permissions (not assigned to workflows), then attempt to access workflow stage and transition data via direct API calls or component views to confirm if sensitive information is accessible without proper authorization
    Affected if The test user can view workflow stage or transition data they were not explicitly permitted to access

The environment is affected if Joomla version is between 6.0.0 and 6.1.1 inclusive, the workflow component is enabled, and unauthorized users can access workflow stage or transition data they should not see.

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 6.1.2 or later
Fixed in 6.1.2
Interim mitigation

Implement and enforce proper authorization checks at all entry points to workflow stage and transition data, ensuring users can only access information for workflows they are explicitly permitted to view.

Recommended fix Moderate confidence

Joomla! 6.1.2 or later

  1. 1. Back up your Joomla! site database and files before proceeding.
  2. 2. Download Joomla! version 6.1.2 or later from the official Joomla! download page (https://downloads.joomla.org/).
  3. 3. Extract the upgrade package to a temporary location on your server.
  4. 4. Use Joomla!'s built-in Update component or overwrite the files via FTP/SFTP, ensuring core files are replaced.
  5. 5. After uploading, navigate to the Joomla! administrator dashboard and complete any database migration steps if prompted.
  6. 6. Verify the installation by logging in and checking that workflow stage and transition information is now properly protected by access controls.
  7. 7. Test that legitimate users with appropriate workflow permissions can still access the features they need.
Caveat Review the Joomla! 6.1.x release notes for any breaking changes between your current version and 6.1.2, particularly regarding workflow component changes

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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