# CVE-2019-16313: Hardcoded credentials in n/a

> Attackers can read the HTML source of usermanager.htm to disclose router credentials, potentially leading to unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j4mf-h43h-v2v6

## What is CVE-2019-16313?

CVE-2019-16313 is a high-severity vulnerability in n/a, published on 14 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ifw8 Router ROM v4.31 allows credential disclosure by reading the action/usermanager.htm HTML source code.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2019-16313?

It affects 5 products.


Products: Ifw8 Fr5-E Firmware, Ifw8 Fr5 Firmware, Ifw8 Fr6-S Firmware, Ifw8 Fr6 Firmware, Ifw8 Fr8 Firmware.

## How do I fix CVE-2019-16313?

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

## Is CVE-2019-16313 being exploited?

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

Public exploit code:

- ifw8 Router ROM v4.31 - Credential Discovery (nuclei): http/cves/2019/CVE-2019-16313.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16313 and fix it if it is affected.

What it is: CVE-2019-16313 is a high-severity vulnerability in n/a, published on 14 Sep 2019. 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-2019-16313 exists.

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-2019-16313/ (Markdown: https://insights.sbomify.com/CVE-2019-16313/index.md)
```

## Sources

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

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