# CVE-2022-34949: SQL injection in n/a

> Attackers can exploit SQL injection in the login form to bypass authentication and access sensitive pharmacy data.

- **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:** 2 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-84mq-285w-hw6j

## What is CVE-2022-34949?

CVE-2022-34949 is a critical SQL injection vulnerability in n/a, published on 2 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pharmacy Management System v1.0 was discovered to contain multiple SQL injection vulnerabilities via the email or password parameter at login.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Pharmacy Management System Project Pharmacy Management System.

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

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

## Is CVE-2022-34949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31519](https://insights.sbomify.com/CVE-2023-31519/): SQL injection in n/a (critical 9.8)
- [CVE-2022-34945](https://insights.sbomify.com/CVE-2022-34945/): SQL injection in n/a (critical 9.8)
- [CVE-2022-34946](https://insights.sbomify.com/CVE-2022-34946/): SQL injection in n/a (critical 9.8)
- [CVE-2022-34947](https://insights.sbomify.com/CVE-2022-34947/): SQL injection in n/a (critical 9.8)
- [CVE-2022-34948](https://insights.sbomify.com/CVE-2022-34948/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34949 is a critical SQL injection vulnerability in n/a, published on 2 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-34949 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-34949/ (Markdown: https://insights.sbomify.com/CVE-2022-34949/index.md)
```

## Sources

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

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