# CVE-2018-15684: Information disclosure in n/a

> Attackers can access predictable PHP error logs in an open directory to obtain sensitive data and full path information.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 5 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hc9c-hrj7-72p6

## What is CVE-2018-15684?

CVE-2018-15684 is a medium-severity vulnerability in n/a, published on 5 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in BTITeam XBTIT. PHP error logs are stored in an open directory (/include/logs) using predictable file names, which can lead to full path disclosure and leakage of sensitive data.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Btiteam Xbtit.

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

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

## Is CVE-2018-15684 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-15680](https://insights.sbomify.com/CVE-2018-15680/): Weak cryptography in n/a (critical 9.8)
- [CVE-2018-15681](https://insights.sbomify.com/CVE-2018-15681/): Weak cryptography in n/a (critical 9.8)
- [CVE-2021-45821](https://insights.sbomify.com/CVE-2021-45821/): SQL injection in n/a (high 8.8)
- [CVE-2018-15682](https://insights.sbomify.com/CVE-2018-15682/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2021-45822](https://insights.sbomify.com/CVE-2021-45822/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15684 is a medium-severity vulnerability in n/a, published on 5 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-15684 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-15684/ (Markdown: https://insights.sbomify.com/CVE-2018-15684/index.md)
```

## Sources

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

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