GHSA-CJCP-QXVG-4RJM

Vulnerability from github – Published: 2025-12-02 00:35 – Updated: 2025-12-02 00:35
VLAI?
Summary
Grav vulnerable to Privilege Escalation in Grav Admin: Missing Username Uniqueness Check Allows Admin Account Takeover
Details

Summary

A privilege escalation vulnerability exists in Grav’s Admin plugin due to the absence of username uniqueness validation when creating users. A user with the create user permission can create a new account using the same username as an existing administrator account, set a new password/email, and then log in as that administrator. This effectively allows privilege escalation from limited user-manager permissions to full administrator access.

Steps to Reproduce

  1. Make sure you have two accounts: an admin and a user with create user privilege
  2. In the user account, navigate to /grav-admin/admin/accounts/users and click "Add"
  3. Enter the name of the admin, complete registration and observe that the existing admin’s email is changed to the value you provided.
  4. Log out from user account log in as admin with new credentials

Impact

  1. Full admin takeover by any user with create user permission.
  2. Ability to change admin credentials, install/remove plugins, read or modify site data, and execute any action available to an admin.
  3. Severity: High/Critical.

PoC

https://github.com/user-attachments/assets/3ab0a7d6-5055-41be-9e0e-2bd6ca359b37

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "getgrav/grav"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.8.0-beta.27"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-66296"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-266"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-12-02T00:35:18Z",
    "nvd_published_at": "2025-12-01T21:15:53Z",
    "severity": "HIGH"
  },
  "details": "### Summary\nA privilege escalation vulnerability exists in Grav\u2019s Admin plugin due to the absence of username uniqueness validation when creating users.\nA user with the create user permission can create a new account using the same username as an existing administrator account, set a new password/email, and then log in as that administrator. This effectively allows privilege escalation from limited user-manager permissions to full administrator access.\n\n\n### Steps to Reproduce\n1. Make sure you have two accounts: an admin and a user with create user privilege\n2. In the user account, navigate to /grav-admin/admin/accounts/users and click \"Add\"\n3. Enter the name of the admin, complete registration and observe that the existing admin\u2019s email is changed to the value you provided.\n4. Log out from user account log in as admin with new credentials\n\n\n### Impact\n1. Full admin takeover by any user with create user permission.\n2. Ability to change admin credentials, install/remove plugins, read or modify site data, and execute any action available to an admin.\n3. Severity: High/Critical.\n\n\n### PoC\nhttps://github.com/user-attachments/assets/3ab0a7d6-5055-41be-9e0e-2bd6ca359b37",
  "id": "GHSA-cjcp-qxvg-4rjm",
  "modified": "2025-12-02T00:35:19Z",
  "published": "2025-12-02T00:35:18Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/getgrav/grav/security/advisories/GHSA-cjcp-qxvg-4rjm"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-66296"
    },
    {
      "type": "WEB",
      "url": "https://github.com/getgrav/grav/commit/3462d94d575064601689b236508c316242e15741"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/getgrav/grav"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Grav vulnerable to Privilege Escalation in Grav Admin: Missing Username Uniqueness Check Allows Admin Account Takeover"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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…