# CVE-2025-8484: Code Quality Control Tool <= 2.1 - Unauthenticated Information Exposure via Log Files

> Unauthenticated attackers can view sensitive information in publicly exposed log files of the Code Quality Control Tool WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/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:** 11 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r6ch-qrwf-wmgv

## What is CVE-2025-8484?

CVE-2025-8484 is a medium-severity vulnerability in nickclarkweb Code Quality Control Tool, published on 11 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Code Quality Control Tool plugin for WordPress is vulnerable to Sensitive Information Exposure in version 2.1 through publicly exposed log files. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed log files.

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

## Which versions are affected by CVE-2025-8484?


## How do I fix CVE-2025-8484?

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

## Is CVE-2025-8484 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8484 and fix it if it is affected.

What it is: CVE-2025-8484 is a medium-severity vulnerability in nickclarkweb Code Quality Control Tool, published on 11 Oct 2025. 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-2025-8484 in the wild and no public exploit code.

Affected product: nickclarkweb Code Quality Control Tool. 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-2025-8484/ (Markdown: https://insights.sbomify.com/CVE-2025-8484/index.md)
```

## Sources

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

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