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

> The Giribaz File Manager plugin logs sensitive wp-config.php contents to a publicly accessible file, exposing database credentials and salts to attackers.

- **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:** 7 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-784x-8m4v-c8cc

## What is CVE-2018-7204?

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

### Official description

inc/logger.php in the Giribaz File Manager plugin before 5.0.2 for WordPress logged activity related to the plugin in /wp-content/uploads/file-manager/log.txt. If a user edits the wp-config.php file using this plugin, the wp-config.php contents get added to log.txt, which is not protected and contains database credentials, salts, etc. These files have been indexed by Google and a simple dork will find affected sites.

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

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

It affects 1 product.


Products: Giribaz File Manager.

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

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

## Is CVE-2018-7204 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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