How many CVEs have patched isValidUsername?

2 published CVEs changed isValidUsername in getgrav/grav, in 1 distinct patches totalling 62 changed lines, between 2025 and 2025.

What is the latest CVE that changed isValidUsername?

CVE-2025-66296 (Grav vulnerable to Privilege Escalation in Grav Admin: Missing Username Uniqueness Check Allows Admin Account Takeover), published 2025-12-01, changed lines 328 to 358 of system/src/Grav/Common/User/DataUser/User.php.

How does isValidUsername compare to the rest of getgrav/grav?

getgrav/grav has 42 CVEs with a located fix in total; 2 of them changed isValidUsername.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

getgrav/grav

Function

isValidUsername

Name: isValidUsername in getgrav/grav: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

system/src/Grav/Common/User/DataUser/User.php

Last patched December 1, 2025

2

CVEs

That changed this function

1

Distinct patches

Backports counted once

62

Lines changed

Added plus removed

2025

Years

By CVE publication date

Overview

isValidUsername in getgrav/grav was changed by 2 published CVE fixes in 2025, in 1 distinct patches that added or removed 62 lines in total.

getgrav/grav has 42 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed isValidUsername, newest first, with the lines each fix touched.

Grav vulnerable to Privilege Escalation in Grav Admin: Missing Username Uniqueness Check Allows Admin Account Takeover
CVE-2025-66296 · lines 328–358 · +31 −0
High · CVSS 8.8
EPSS 0.3%2025-12-01
Grav vulnerable to Path traversal / arbitrary YAML write via user creation leading to Account Takeover / System Corruption
CVE-2025-66295 · lines 328–358 · +31 −0
High · CVSS 8.8
EPSS 0.6%2025-12-01

Get an alert when the next CVE fix lands in getgrav/grav, with the patched functions.

Monitor grav CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in getgrav/grav changed by the most CVE fixes.

detectXss6 CVEs · system/src/Grav/Common/Security.php processPage5 CVEs · system/src/Grav/Common/Twig/Twig.php cleanDangerousTwig5 CVEs · system/src/Grav/Common/Security.php getFlashObject5 CVEs · system/src/Grav/Common/Session.php getFilters4 CVEs · system/src/Grav/Common/Twig/Extension/GravExtension.php save4 CVEs · system/src/Grav/Common/Flex/Types/Users/UserObject.php

All patched functions in getgrav/grav

Frequently asked questions

Common questions about CVE fixes to isValidUsername.

How many CVEs have patched isValidUsername?: 2 published CVEs changed isValidUsername in getgrav/grav, in 1 distinct patches totalling 62 changed lines, between 2025 and 2025.
What is the latest CVE that changed isValidUsername?: CVE-2025-66296 (Grav vulnerable to Privilege Escalation in Grav Admin: Missing Username Uniqueness Check Allows Admin Account Takeover), published 2025-12-01, changed lines 328 to 358 of system/src/Grav/Common/User/DataUser/User.php.
How does isValidUsername compare to the rest of getgrav/grav?: getgrav/grav has 42 CVEs with a located fix in total; 2 of them changed isValidUsername.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track getgrav/grav CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing