# CVE-2019-19018: Information disclosure in n/a

> An attacker can access a database configuration file via the web interface, revealing database details in WebTitan.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-32f2-v4v8-76vw

## What is CVE-2019-19018?

CVE-2019-19018 is a low-severity vulnerability in n/a, published on 2 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in TitanHQ WebTitan before 5.18. It exposes a database configuration file under /include/dbconfig.ini in the web administration interface, revealing what database the web application is using.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 1 product.


Products: Titanhq Webtitan.

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

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

## Is CVE-2019-19018 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19015](https://insights.sbomify.com/CVE-2019-19015/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-19021](https://insights.sbomify.com/CVE-2019-19021/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-19017](https://insights.sbomify.com/CVE-2019-19017/): Hardcoded credentials in n/a (high 8.1)
- [CVE-2019-19014](https://insights.sbomify.com/CVE-2019-19014/): Privilege escalation in n/a (high 7.8)
- [CVE-2019-19016](https://insights.sbomify.com/CVE-2019-19016/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19018 is a low-severity vulnerability in n/a, published on 2 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19018 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-2019-19018/ (Markdown: https://insights.sbomify.com/CVE-2019-19018/index.md)
```

## Sources

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

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