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

> Remote attackers can access sensitive log files directly via URL, exposing potentially confidential data in GreenCMS.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 20 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2939-pqmr-4866

## What is CVE-2018-12604?

CVE-2018-12604 is a high-severity vulnerability in n/a, published on 20 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GreenCMS 2.3.0603 allows remote attackers to obtain sensitive information via a direct request for Data/Log/year_month_day.log.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Njtech Greencms.

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

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

## Is CVE-2018-12604 being exploited?

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

Public exploit code:

- GreenCMS 2.3.0603 - Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-11670](https://insights.sbomify.com/CVE-2018-11670/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-11671](https://insights.sbomify.com/CVE-2018-11671/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-28918](https://insights.sbomify.com/CVE-2022-28918/): Path traversal in n/a (high 8.1)
- [CVE-2020-21366](https://insights.sbomify.com/CVE-2020-21366/): Cross-site request forgery in n/a (high 8.0)
- [CVE-2019-25573](https://insights.sbomify.com/CVE-2019-25573/): Green CMS 2.x SQL Injection via cat Parameter (high 7.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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