dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-44262

CRITICAL · 9.4 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Scramble generates API documentation for Laravel project. From 0.13.2 to before 0.13.22, 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. This vulnerability is fixed in 0.13.22.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Scramble (Laravel API documentation package) versions 0.13.2 through 0.13.21 allow arbitrary PHP code execution when documentation endpoints are publicly accessible and validation rules reference user-controlled input. The request data gets evaluated during documentation generation, enabling attackers to execute arbitrary PHP code in the application context.

MitigationUpgrade Scramble to version 0.13.22 or later, and ensure documentation endpoints require authentication rather than being publicly accessible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Scramble version
    Run 'composer show scramble/core' or check the version listed in composer.lock under packages/scramble/core, or inspect composer.json for the scramble version requirement
    Affected if version is 0.13.2, 0.13.3, 0.13.4, 0.13.5, 0.13.6, 0.13.7, 0.13.8, 0.13.9, 0.13.10, 0.13.11, 0.13.12, 0.13.13, 0.13.14, 0.13.15, 0.13.16, 0.13.17, 0.13.18, 0.13.19, 0.13.20, or 0.13.21
  2. Verify documentation endpoint accessibility
    Inspect routes/api.php, routes/web.php, or routes/docs.php for Scramble documentation routes (typically /docs or /api/docs). Check if these routes have auth middleware applied (such as 'auth', 'auth:sanctum', or custom authentication guards)
    Affected if documentation endpoints are accessible without any authentication middleware (no auth:sanctum, auth:api, or similar guard)
  3. Inspect validation rules for user-controlled input
    Review controller validation rules that handle API requests, particularly looking for Rule::when, Rule::if, or custom validation logic that references $request->input(), request()->, or similar user-supplied data in validation rule definitions
    Affected if validation rules used in API endpoints dynamically incorporate user request data (for example, using $request->input() within Rule::when conditions or conditional validation logic)

Environment is affected only if Scramble version is between 0.13.2 and 0.13.21 AND documentation endpoints are publicly accessible AND application validation rules reference user-controlled input in the request flow

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Scramble to version 0.13.22 or later, and ensure documentation endpoints require authentication rather than being publicly accessible.

Recommended fix Moderate confidence

scrambledocs/scramble version 0.13.22

  1. Check the current version of scrambledocs/scramble in your project using `composer show scrambledocs/scramble` or by checking your composer.lock file
  2. Run `composer update scrambledocs/scramble:0.13.22` or `composer require scrambledocs/scramble:^0.13.22` to upgrade to the fixed version
  3. Verify the installation was successful by running `composer show scrambledocs/scramble` and confirming version 0.13.22 or later is installed
  4. Review your documentation endpoint access controls to ensure they are not publicly accessible if not intentionally required
  5. Test that your API documentation generation still functions correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44262 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data