# CVE-2021-41931: SQL injection in n/a

> An attacker can exploit SQL injection in the recruitment system's vacancy view to read or modify database contents.

- **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:** 17 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-95rh-p2cc-63r3

## What is CVE-2021-41931?

CVE-2021-41931 is a critical SQL injection vulnerability in n/a, published on 17 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Company's Recruitment Management System in id=2 of the parameter from view_vacancy app on-page appears to be vulnerable to SQL injection. The payloads 19424269' or '1309'='1309 and 39476597' or '2917'='2923 were each submitted in the id parameter. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.

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

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

It affects 1 product.


Products: Recruitment Management System Project Recruitment Management System.

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

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

## Is CVE-2021-41931 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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