CVE-2021-26800
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 · uneditedCross Site Request Forgery (CSRF) vulnerability in Change-password.php in phpgurukul user management system in php using stored procedure V1.0, allows attackers to change the password to an arbitrary account.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Change-password.php script of the phpgurukul user management system V1.0 allows an attacker to craft a malicious request that tricks an authenticated user into changing their password to an arbitrary value without their consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed product and versionLocate the project files or admin interface to confirm the User Management System version is 1.0. Check for version identifiers in source files, readme, or about pages.Affected if The installed version is User Management System In Php Stored Procedure version 1.0.
-
Locate the Change-password.php scriptSearch the web root directory for the file named 'Change-password.php' or 'change-password.php'. This is typically found in the user or admin dashboard directories.Affected if The Change-password.php script exists in the application directory.
-
Inspect the password change form for CSRF token fieldOpen the Change-password.php file in a text editor or view the page source in a browser. Look for an input field with type='hidden' containing a token value, such as 'csrf_token', 'token', or 'csrf' in the form markup.Affected if The password change form does NOT contain a hidden CSRF token field.
-
Verify server-side token validation logicIn Change-password.php, search for code that retrieves and validates a CSRF token on form submission. Look for functions like $_POST['csrf_token'] comparison, session token verification, or similar anti-CSRF validation routines.Affected if The script lacks server-side validation of a CSRF token before processing password changes.
-
Check for SameSite cookie configurationExamine the session configuration or cookie headers in the application. Look for 'SameSite' attribute being set to 'Strict' or 'Lax' on session cookies in the PHP configuration or code.Affected if SameSite cookie attributes are not configured for session cookies.
You are affected if you are running phpgurukul User Management System version 1.0 and the Change-password.php script does not implement and validate anti-CSRF tokens on the password change form.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement anti-CSRF tokens (synchronizer token pattern) on the password change form and validate them during form processing. Additionally, configure SameSite cookie attributes and validate Origin/Referer headers.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26800 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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