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

> Attackers can access sensitive audit log files via public URLs, potentially exposing confidential information to unauthorized users.

- **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:** 4 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m2v4-55f4-q786

## What is CVE-2018-8719?

CVE-2018-8719 is a medium-severity vulnerability in n/a, published on 4 Apr 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 the WP Security Audit Log plugin 3.1.1 for WordPress. Access to wp-content/uploads/wp-security-audit-log/* files is not restricted. For example, these files are indexed by Google and allows for attackers to possibly find sensitive information.

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

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

It affects 1 product.


Products: Wpsecurityauditlog Wp Security Audit Log.

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

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

## Is CVE-2018-8719 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-8719 exists.

Public exploit code:

- WordPress Plugin WP Security Audit Log 3.1.1 - Sensitive Information Disclosure (exploitdb)
- WordPress WP Security Audit Log 3.1.1 - Information Disclosure (nuclei): http/cves/2018/CVE-2018-8719.yaml

## Other vulnerabilities in n/a

- [CVE-2014-5072](https://insights.sbomify.com/CVE-2014-5072/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8719 is a medium-severity vulnerability in n/a, published on 4 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-8719 exists.

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-8719/ (Markdown: https://insights.sbomify.com/CVE-2018-8719/index.md)
```

## Sources

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

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