PHP file inclusion in the Sulu admin panel

Exploitation

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

CVSS

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

EPSS

• CVE-2021-43836: 2.05% estimated exploitation activity in the next 30 days; percentile 81.23 (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 What kind of vulnerability is it? Who is impacted? An attacker can read arbitrary local files via a PHP file include. In a default configuration this also leads to remote code execution. Compromised components: Arbitrary file read on the server, (Potential) Remote code execution Exploitation pre-requisite: User account on the backend Patches Has the problem been patched? What versions should users upgrade to? The problem is patched with the Versions 1.6.44, 2.2.18, 2.3.8, 2.4.0 Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? Overwrite the service suluroute.generator.expressiontokenprovider and wrap the translator before passing it to the expression language. References Are there any links users can visit to find out more? Currently not. For more information If you have any questions or comments about this advisory: Open an issue in example link to repo Email us at example email address

Published by the source

15 Dec 2021, 22:54 UTC

Last modified by the source

1 Feb 2023, 05:07 UTC

Source last checked

26 Oct 2026, 14:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vx6j-pjrh-vgjh

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

# Patch Next advisory brief: CVE-2021-43836

Advisory: PHP file inclusion in the Sulu admin panel
IDs: CVE-2021-43836, GHSA-vx6j-pjrh-vgjh
Record: https://patchnext.com/advisories/cve-2021-43836 (revision 1, source checked 26 Oct 2026, 14:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sulu/sulu 2.4.0, 2.3.8, 2.2.18, 1.6.44. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sulu/sulu: affected < 1.6.44; >= 2.0.0, < 2.2.18; >= 2.3.0, < 2.3.8; >= 2.4.0-RC1, <= 2.4.0-RC1; fixed in 2.4.0, 1.6.44, 2.2.18, 2.3.8

## Suggested inspection (read-only)
- Packagist sulu/sulu: 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 sulu/sulu.
- 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-vx6j-pjrh-vgjh (GitHub-reviewed advisory GHSA-vx6j-pjrh-vgjh lists affected ranges: Packagist sulu/sulu >=0 =2.0.0 =2.3.0 =2.4.0-RC1 <=2.4.0-RC1)

Commands are suggestions: review each one before running it.