# CVE-2018-16286: Auth bypass in n/a

> Attackers can bypass authentication in LG SuperSign CMS by sending a specific cookie and exploiting weak PIN constraints.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 14 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qc57-qhfx-p8p2

## What is CVE-2018-16286?

CVE-2018-16286 is a critical authentication bypass vulnerability in n/a, published on 14 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LG SuperSign CMS allows authentication bypass because the CAPTCHA requirement is skipped if a captcha:pass cookie is sent, and because the PIN is limited to four digits.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-16286?

It affects 1 product.


Products: Lg Supersign Cms.

## How do I fix CVE-2018-16286?

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

## Is CVE-2018-16286 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-17173](https://insights.sbomify.com/CVE-2018-17173/): Code injection in n/a (critical 9.8)
- [CVE-2018-16287](https://insights.sbomify.com/CVE-2018-16287/): File upload in n/a (critical 9.8)
- [CVE-2018-16288](https://insights.sbomify.com/CVE-2018-16288/): Path traversal in n/a (high 8.6)
- [CVE-2018-16706](https://insights.sbomify.com/CVE-2018-16706/): Missing authorization in n/a (high 7.5)
- [CVE-2024-6177](https://insights.sbomify.com/CVE-2024-6177/): XSS vulnerability in LG SuperSign CMS (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16286 and fix it if it is affected.

What it is: CVE-2018-16286 is a critical authentication bypass vulnerability in n/a, published on 14 Sep 2018. 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-2018-16286 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-2018-16286/ (Markdown: https://insights.sbomify.com/CVE-2018-16286/index.md)
```

## Sources

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

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