# CVE-2017-20127: KB Login Authentication Script sql injection

> Remote attackers can exploit SQL injection in the login script to bypass authentication and access sensitive data.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-9x3j-jm5p-ww3p

## What is CVE-2017-20127?

CVE-2017-20127 is a high-severity SQL injection vulnerability in unspecified KB Login Authentication Script, published on 13 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in KB Login Authentication Script 1.1 and classified as critical. Affected by this issue is some unknown functionality. The manipulation of the argument username/password with the input 'or''=' leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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

## Which versions are affected by CVE-2017-20127?

It affects 1 product.


Products: Kb Login Authentication Script Project Kb Login Authentication Script.

## How do I fix CVE-2017-20127?

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

## Is CVE-2017-20127 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20127 and fix it if it is affected.

What it is: CVE-2017-20127 is a high-severity SQL injection vulnerability in unspecified KB Login Authentication Script, published on 13 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20127 exists.

Affected product: unspecified KB Login Authentication Script. 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-2017-20127/ (Markdown: https://insights.sbomify.com/CVE-2017-20127/index.md)
```

## Sources

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

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