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

> Monstra CMS exposes sensitive server configuration details like paths and admin emails in error messages, allowing attackers to gather reconnaissance data.

- **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:** 12 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-87h5-4h68-r79h

## What is CVE-2018-16977?

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

### Official description

Monstra CMS V3.0.4 has an information leakage risk (e.g., PATH, DOCUMENT_ROOT, and SERVER_ADMIN) in libraries/Gelato/ErrorHandler/Resources/Views/Errors/exception.php.

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

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

It affects 1 product.


Products: Monstra Monstra.

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

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

## Is CVE-2018-16977 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-40940](https://insights.sbomify.com/CVE-2021-40940/): File upload in n/a (critical 9.8)
- [CVE-2021-36548](https://insights.sbomify.com/CVE-2021-36548/): File upload in n/a (critical 9.8)
- [CVE-2020-25414](https://insights.sbomify.com/CVE-2020-25414/): Code injection in n/a (critical 9.8)
- [CVE-2020-13384](https://insights.sbomify.com/CVE-2020-13384/): File upload in n/a (high 8.8)
- [CVE-2018-16608](https://insights.sbomify.com/CVE-2018-16608/): Missing authorization in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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