# CVE-2022-38813: Missing authorization in n/a

> Attackers can access, delete, and modify user data and manage blood groups in the Blood Donor Management System due to missing authorization checks on the admin dashboard.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2022
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-x3p3-x38c-j2c6

## What is CVE-2022-38813?

CVE-2022-38813 is a high-severity missing authorization vulnerability in n/a, published on 25 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PHPGurukul Blood Donor Management System 1.0 does not properly restrict access to admin/dashboard.php, which allows attackers to access all data of users, delete the users, add and manage Blood Group, and Submit Report.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2022-38813?

It affects 1 product.


Products: Phpgurukul Blood Donor Management System Project Phpgurukul Blood Donor Management System.

## How do I fix CVE-2022-38813?

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

## Is CVE-2022-38813 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38813 exists.

Public exploit code:

- Authenticated Vertical Privilege Escalation Vulnerability in Blood Donor Management System (github_poc): https://github.com/RashidKhanPathan/CVE-2022-38813

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38813 and fix it if it is affected.

What it is: CVE-2022-38813 is a high-severity missing authorization vulnerability in n/a, published on 25 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38813 exists.

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-2022-38813/ (Markdown: https://insights.sbomify.com/CVE-2022-38813/index.md)
```

## Sources

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

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