# CVE-2021-26800: Cross-site request forgery in n/a

> Attackers can force users to change their passwords via CSRF, leading to account takeover in the user management system.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-789w-f5ch-wrjq

## What is CVE-2021-26800?

CVE-2021-26800 is a medium-severity vulnerability in n/a, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-26800?

It affects 1 product.


Products: User Management System in Php Stored Procedure Project User Management System in Php Stored Procedure.

## How do I fix CVE-2021-26800?

No fix has been published for CVE-2021-26800 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-26800 being exploited?

There is no known exploitation of CVE-2021-26800 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26800 and fix it if it is affected.

What it is: CVE-2021-26800 is a medium-severity vulnerability in n/a, published on 16 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-26800 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-26800/ (Markdown: https://insights.sbomify.com/CVE-2021-26800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-26800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-26800
- OSV: https://osv.dev/vulnerability/CVE-2021-26800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-26800/
Summaries are generated and may contain mistakes; the official description above is the record.