# CVE-2022-28601: Auth bypass in n/a

> Remote attackers can bypass two-factor authentication by overwriting the confirmation phone number via the profile page.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 10 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-pghm-m86j-5288

## What is CVE-2022-28601?

CVE-2022-28601 is a medium-severity authentication bypass vulnerability in n/a, published on 10 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Two-Factor Authentication (2FA) bypass vulnerability in "Simple 2FA Plugin for Moodle" by LMS Doctor allows remote attackers to overwrite the phone number used for confirmation via the profile.php file. Therefore, allowing them to bypass the phone verification mechanism.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Lmsdoctor 2 Factor Authentication.

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

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

## Is CVE-2022-28601 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28986](https://insights.sbomify.com/CVE-2022-28986/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28601 is a medium-severity authentication bypass vulnerability in n/a, published on 10 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28601 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-28601/ (Markdown: https://insights.sbomify.com/CVE-2022-28601/index.md)
```

## Sources

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

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