{
  "id": "CVE-2026-92594",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-92594",
  "published_at": "2026-09-16T21:46:59.423Z",
  "title": "Craft CMS before 5.11.0 Unauthenticated PII Disclosure via GraphQL",
  "vendor": "craftcms",
  "product": "cms",
  "cvss": {
    "score": 8.7,
    "source": "cna",
    "vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  },
  "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": "Craft CMS 5.0.0-RC1 through versions before 5.11.0 incorrectly authorize the GraphQL draftCreator and revisionCreator fields: instead of requiring the user-data scope enforced by Gql::canQueryUsers() (usergroups.*:read), these fields are gated only on the elements.drafts:read / elements.revisions:read scopes, and their resolver returns a raw User element whose email, username, fullName, and addresses fields have no per-field authorization. A client holding only the drafts or revisions scope — including an unauthenticated client when the operator has enabled the public GraphQL schema with those scopes — can therefore harvest the email addresses, usernames, full names, and postal addresses of all draft/revision creators (typically site editors and administrators). The issue is fixed in 5.11.0.",
  "cwe": "CWE-200",
  "cvss_by_source": {
    "cna": 8.7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "craftcms",
        "product": "cms",
        "ranges": [
          "\u003e= 5.0.0-RC1, \u003c 5.11.0"
        ],
        "fixed_in": [
          "5.11.0"
        ]
      }
    ],
    "upgrade": [
      "Upgrade cms to 5.11.0 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/craftcms/cms/security/advisories/GHSA-pcmv-c398-gc5m"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
