{
  "id": "CVE-2026-110911",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-110911",
  "published_at": "2026-10-15T03:03:49.507Z",
  "vendor": "Wheels",
  "product": "Wheels",
  "cvss": {
    "score": 9.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "Wheels 1.1.8 through 4.1.1 allows SQL injection when caller-supplied quoted values are parsed again as SQL by dynamic finders (such as findOneByEmail), the query builder's where(property, value) and where(property, operator, value), string/UUID-key lookup paths (findByKey, updateByKey, deleteByKey and findOrCreateBy...), and validatesUniquenessOf. The parser incorrectly treats a doubled single quote as the end of a literal. Applications passing request data to these APIs can expose authentication, password-reset or token lookups, and data to unauthorized access; numeric-column values are not affected. There is a similar concern for query-builder whereBetween() in 4.0.0 through 4.1.1: string/date bounds can alter SQL on MySQL/MariaDB with backslash escaping enabled. This is fixed in 4.1.2.",
  "cwe": "CWE-89",
  "cvss_by_source": {
    "cna": 9.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Wheels",
        "product": "Wheels",
        "ranges": [
          "\u003e= 1.1.8, \u003c 4.1.2"
        ],
        "fixed_in": [
          "4.1.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Wheels to 4.1.2 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/wheels-dev/wheels/security/advisories/GHSA-96rm-h22v-925x"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
