dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-59190

HIGH · 8.7 CVSS v4.0 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 6 weeks old

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
grav-plugin-admin is an HTML user interface that provides a way to configure Grav and create and modify pages. In 1.10.52 and earlier, an authenticated attacker with admin.users permission can change the password of any user account, including the super administrator, by sending a direct POST request to /admin/user/{username}?task=save with data[password] because saveUser authorizes the caller's user-management permission but does not verify whether the caller may edit the target user. This issue is expected to be fixed in version 1.10.53.

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

grav-plugin-admin versions 1.10.52 and earlier contain an Insecure Direct Object Reference (IDOR) vulnerability in the saveUser function. An authenticated attacker with admin.users permission can change any user's password, including the super administrator, by sending a direct POST request to /admin/user/{username}?task=save with a crafted data[password] parameter. The function properly checks the caller's general user-management permission but fails to verify whether the caller is authorized to modify the specific target user.

MitigationUpgrade to grav-plugin-admin version 1.10.53 or later. Until a patch is available, restrict admin.users permission to only highly trusted users and consider implementing additional access controls at the web server layer for user management endpoints.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm grav-plugin-admin is installed
    Locate the Grav CMS installation and identify if the admin plugin (grav-plugin-admin) is present in the plugins directory.
    Affected if The plugin is not installed, the system is not affected by this specific vulnerability.
  2. Determine installed plugin version
    Access the plugin's version information through the Grav admin dashboard (Extensions > Plugins > Admin) or inspect the plugin's manifest/configuration file.
    Affected if The installed version is 1.10.52 or earlier, placing it within the vulnerable range.
  3. Verify admin.users permission configuration
    Check the user permissions configuration in Grav CMS to determine which users or groups have the admin.users permission assigned.
    Affected if Any user account other than the super administrator has admin.users permission, creating a potential attacker with exploitation capability.
  4. Confirm admin panel accessibility
    Verify that the /admin/user endpoint is accessible over the network. Check web server access logs for requests to /admin/user/{username}?task=save patterns.
    Affected if The admin panel is externally accessible and admin.users permission exists for non-super-admin accounts, the IDOR can be exploited.

A user is affected if grav-plugin-admin version 1.10.52 or earlier is installed AND the admin.users permission is assigned to any authenticated user other than the super administrator, with the admin interface network-accessible.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to grav-plugin-admin version 1.10.53 or later. Until a patch is available, restrict admin.users permission to only highly trusted users and consider implementing additional access controls at the web server layer for user management endpoints.

Recommended fix High confidence

grav-plugin-admin version 1.10.53

  1. 1. Backup your Grav installation and database before proceeding
  2. 2. Navigate to your Grav project directory
  3. 3. Update grav-plugin-admin to version 1.10.53 or later using Composer: composer update getgrav/grav-plugin-admin
  4. 4. Alternatively, if using Grav's built-in updater, navigate to Admin panel > Plugins > Admin and check for updates
  5. 5. Clear any caching after the update: bin/grav clear-cache
  6. 6. Verify the update was successful by checking the plugin version in Admin > Plugins > Admin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59190 — 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-59190 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