GHSA-vx6j-pjrh-vgjh
HIGHPHP file inclusion in the Sulu admin panel
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
sulu/sulu🐘sulu/sulu🐘sulu/sulu🐘sulu/suluReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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 sulu_route.generator.expression_token_provider 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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | sulu/sulu | all versions | 1.6.44 |
| 🐘Packagist | sulu/sulu | ≥ 2.0.0&&< 2.2.18 | 2.2.18 |
| 🐘Packagist | sulu/sulu | ≥ 2.3.0&&< 2.3.8 | 2.3.8 |
| 🐘Packagist | sulu/sulu | ≥ 2.4.0-RC1&&< 2.4.0 | 2.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sulu/sulu. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sulu/sulu to 1.6.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vx6j-pjrh-vgjh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-vx6j-pjrh-vgjh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vx6j-pjrh-vgjh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vx6j-pjrh-vgjh in your dependencies?
O3 detects GHSA-vx6j-pjrh-vgjh across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.