GHSA-p46m-g734-vpc4: Medium severity composer/cakephp/debug_kit vulnerability

Published Aug 26, 2026
·
Updated

Impact

The MailPreview feature of debugkit is vulnerable to arbitrary constructor execution. For an application to be vulnerable the following conditions must be true:

1. debug mode must be enabled. 2. The hostname must match a 'local' domain or be in an allowlist.

Patches 5.2.4 and 4.10.3 contain patches for this issue.

Workarounds Ensure that debugkit is only part of your development dependencies, and that debug mode is disabled in production environments.

Affected Software

2 affected componentsFixes available
composer/cakephp/debug_kit>=5.0.0<5.2.4
5.2.4
composer/cakephp/debug_kit<4.10.3
4.10.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/cakephp/debug_kit to a version that resolves this vulnerability.

    Fixed in 5.2.4
  2. Upgrade

    Upgrade composer/cakephp/debug_kit to a version that resolves this vulnerability.

    Fixed in 4.10.3
  3. Upgrade

    Upgrade debugkit to a version that resolves this vulnerability.

    Fixed in 5.2.4
  4. Upgrade

    Upgrade debugkit to a version that resolves this vulnerability.

    Fixed in 4.10.3
  5. Configuration

    Ensure debugkit is only part of your development dependencies (i.e., not included in production).

    debugkit MailPreview feature = development dependencies only
  6. Configuration

    Disable debug mode in production environments so `debug` is not enabled.

    debugkit debug mode = disabled

Event History

Aug 26, 2026
Advisory Published
via GitHub·03:31 PM
Data Sourced
via GitHub·03:31 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

An application is vulnerable only when debug mode is enabled and the request hostname matches a local domain or is included in an allowlist. Production deployments with debug mode disabled do not meet the stated conditions.

2

What level of access does an attacker need?

The supplied vector indicates network-reachable exploitation with low privileges required and no user interaction. The issue allows arbitrary constructor execution through the MailPreview feature when the vulnerable conditions are present.

3

Which releases contain a fix?

The issue is patched in debugkit versions 5.2.4 and 4.10.3.

4

What can be done before updating?

Keep debugkit limited to development dependencies and disable debug mode in production environments. This prevents the stated vulnerable deployment condition in production.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203