GHSA-4RM2-28VJ-FJ39

Vulnerability from github – Published: 2026-05-06 19:54 – Updated: 2026-05-13 16:41
VLAI
Summary
Scramble vulnerable to remote code execution via evaluation of user-controlled input in validation rules
Details

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.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.13.21"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "dedoc/scramble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.13.2"
            },
            {
              "fixed": "0.13.22"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-44262"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-94"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-06T19:54:56Z",
    "nvd_published_at": "2026-05-12T22:16:36Z",
    "severity": "CRITICAL"
  },
  "details": "### Impact\n\nA 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.\n\n### Patches\n\nFixed in version `0.13.22`.\n\n### Workarounds\n\nIf upgrading is not immediately possible:\n\n* Restrict access to documentation endpoints (`/docs/api`, `/docs/api.json`)\n* Avoid using user-controlled variables inside validation rule expressions (e.g., values derived from request input)\n* Disable documentation endpoints in production environments if not required\n\nThese measures significantly reduce or prevent exploitability.",
  "id": "GHSA-4rm2-28vj-fj39",
  "modified": "2026-05-13T16:41:47Z",
  "published": "2026-05-06T19:54:56Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/dedoc/scramble/security/advisories/GHSA-4rm2-28vj-fj39"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44262"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/dedoc/scramble"
    },
    {
      "type": "WEB",
      "url": "https://github.com/dedoc/scramble/releases/tag/v0.13.22"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Scramble vulnerable to remote code execution via evaluation of user-controlled input in validation rules"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…