Potential unauthorized access to stored request & session data when plugin is misconfigured in October CMS Debugbar

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS

• CVE-2020-11094: 1.05% estimated exploitation activity in the next 30 days; percentile 64.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The debugbar contains a perhaps little known feature where it will log all requests (and all information pertaining to each request including session data) whenever it is enabled. This presents a problem if the plugin is ever enabled on a system that is open to untrusted users as the potential exists for them to use this feature to view all requests being made to the application and obtain sensitive information from those requests. There even exists the potential for account takeovers of authenticated users by non-authenticated public users, which would then lead to a number of other potential issues as an attacker could theoretically get full access to the system if the required conditions existed. Patches Issue has been patched in v3.1.0 by locking down access to the debugbar to all users; it now requires an authenticated backend user with a specifically enabled permission before it is even usable, and the feature that allows access to stored request information is…

Published by the source

3 Jun 2020, 23:19 UTC

Last modified by the source

9 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 13:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c8wh-6jw4-2h79

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11094

Advisory: Potential unauthorized access to stored request & session data when plugin is misconfigured in October CMS Debugbar
IDs: CVE-2020-11094, GHSA-c8wh-6jw4-2h79
Record: https://patchnext.com/advisories/cve-2020-11094 (revision 1, source checked 26 Oct 2026, 13:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rainlab/debugbar-plugin 3.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist rainlab/debugbar-plugin: affected < 3.1.0; fixed in 3.1.0

## Suggested inspection (read-only)
- Packagist rainlab/debugbar-plugin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rainlab/debugbar-plugin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c8wh-6jw4-2h79 (GitHub-reviewed advisory GHSA-c8wh-6jw4-2h79 lists affected ranges: Packagist rainlab/debugbar-plugin >=0 <3.1.0)

Commands are suggestions: review each one before running it.