# CVE-2017-20066: Adminer Login access control

> An attacker with local access can bypass authentication controls in Adminer Login to gain unauthorized access to the application.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-3754-735c-c4rm

## What is CVE-2017-20066?

CVE-2017-20066 is a medium-severity missing authorization vulnerability in unspecified Adminer Login, published on 20 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in Adminer Login 1.4.4 and classified as problematic. This vulnerability affects unknown code. The manipulation leads to improper access controls. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

Weakness: CWE-863 (Incorrect Authorization), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Adminer Login Project Adminer Login.

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

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

## Is CVE-2017-20066 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20066 is a medium-severity missing authorization vulnerability in unspecified Adminer Login, published on 20 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20066 exists.

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

## Sources

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

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