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

> Attackers can access or modify other patients' settings by manipulating the ID parameter in the settings page.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-m6pw-38q3-7wrw

## What is CVE-2022-36202?

CVE-2022-36202 is a critical missing authorization vulnerability in n/a, published on 31 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Doctor's Appointment System1.0 is vulnerable to Incorrect Access Control via edoc/patient/settings.php. The settings.php is affected by Broken Access Control (IDOR) via id= parameter.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Doctor\'s Appointment System Project Doctor\'s Appointment System.

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

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

## Is CVE-2022-36202 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36201](https://insights.sbomify.com/CVE-2022-36201/): SQL injection in n/a (critical 9.8)
- [CVE-2022-36203](https://insights.sbomify.com/CVE-2022-36203/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36202 is a critical missing authorization vulnerability in n/a, published on 31 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36202 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-2022-36202/ (Markdown: https://insights.sbomify.com/CVE-2022-36202/index.md)
```

## Sources

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

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