GHSA-4rm2-28vj-fj39 — dedoc/scramble
CRITICALGHSA-4rm2-28vj-fj39 is a critical-severity (CVSS 9.4) Code Injection vulnerability in dedoc/scramble. 2 public exploit references exist, so weaponization risk is real. A fix is available for dedoc/scramble — see the affected versions and patch details below.
Scramble vulnerable to remote code execution via evaluation of user-controlled input in validation rules
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4rm2-28vj-fj39.
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.
How urgent is this, really
GHSA-4rm2-28vj-fj39 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
dedoc/scrambleReal-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
A remote code execution (RCE) vulnerability affects versions 0.13.2 through 0.13.21. When documentation endpoints are publicly accessible and validation rules reference user-controlled input, request supplied data may be evaluated during documentation generation, leading to execution of arbitrary PHP code in the application context.
Patches
Fixed in version 0.13.22.
Workarounds
If upgrading is not immediately possible:
- Restrict access to documentation endpoints (
/docs/api,/docs/api.json) - Avoid using user-controlled variables inside validation rule expressions (e.g., values derived from request input)
- Disable documentation endpoints in production environments if not required
These measures significantly reduce or prevent exploitability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | dedoc/scramble | ≥ 0.13.2&&< 0.13.22 | 0.13.22composer require dedoc/scramble:^0.13.22 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
scramble - Remote Code Execution
by joshua · May 27, 2026
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dedoc/scramble, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dedoc/scramble to 0.13.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rm2-28vj-fj39 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4rm2-28vj-fj39 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4rm2-28vj-fj39. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-4rm2-28vj-fj39
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-4rm2-28vj-fj39 -u https://target- Template
- Scramble Laravel - Remote Code Execution
- Severity
- critical
- Impact
- Remote attackers can execute arbitrary PHP code, potentially leading to full application compromise.
- Remediation
- Upgrade to version 0.13.22 or later.
Template by ProjectDiscovery nuclei-templates (joshuavanderpoll), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-4rm2-28vj-fj39 in your dependencies?
O3 Security finds GHSA-4rm2-28vj-fj39 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.