The Grav Login plugin (grav-plugin-login) versions <= 3.8.11 contain a privilege escalation flaw in the authenticated profile self-update handler (processUserProfile(), the update_user task). Unlike the registration handler, this handler does not strip privilege fields ('groups','access') from user-submitted form data before persisting them. When an administrator has added 'groups' and/or 'access' to plugins.login.user_registration.fields and the default 'regular'/DataUser account backend is in use, a low-privilege authenticated user can POST crafted profile form data (e.g. access[admin][super]=true) to escalate to super-admin, enabling admin panel access, scheduler abuse (RCE), and Twig evaluation. Fixed in 3.8.12.
CVE-2026-65603
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EPSS
- —
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 22, 2026Grav Login Plugin 3.8.11 Privilege Escalation via Profile Update | Advisories | VulnCheck
https://www.vulncheck.com/advisories/grav-login-plugin-privilege-escalation-via-profile-updatePrivilege escalation via profile self-update (update_user) mass-assignment of groups/access on default backend · Advisory · getgrav/grav · GitHub
https://github.com/getgrav/grav/security/advisories/GHSA-h33v-82r9-v8pmVendor Advisories for CVE-2026-65603(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 13:35 UTCEG score recompute
- 2026-07-22 13:35 UTCGHSA enrichment
- 2026-07-22 11:32 UTCEG score recompute
- 2026-07-22 11:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(4)
What is CVE-2026-65603?
When was CVE-2026-65603 disclosed?
What is the CVSS score of CVE-2026-65603?
How do I remediate CVE-2026-65603?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65603
Is Your Infrastructure Affected by CVE-2026-65603?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.