# CVE-2024-6569: Campaign Monitor for WordPress <= 2.8.15 - Unauthenticated Full Path Disclosure

> Unauthenticated attackers can retrieve the full web application path via direct access to an admin file, aiding further attacks.

- **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:** 27 Jul 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-27h8-4rhj-pqp5

## What is CVE-2024-6569?

CVE-2024-6569 is a medium-severity vulnerability in vibhorchhabra Campaign Monitor for WordPress, published on 27 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Campaign Monitor for WordPress plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.8.15. This is due the plugin not properly restricting direct access to /forms/views/admin/create.php and display_errors being enabled. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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

## Which versions are affected by CVE-2024-6569?


## How do I fix CVE-2024-6569?

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

## Is CVE-2024-6569 being exploited?

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

Public exploit code:

- Campaign Monitor for WordPress - Information Disclosure (nuclei): http/cves/2024/CVE-2024-6569.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6569 and fix it if it is affected.

What it is: CVE-2024-6569 is a medium-severity vulnerability in vibhorchhabra Campaign Monitor for WordPress, published on 27 Jul 2024. 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-2024-6569 exists.

Affected product: vibhorchhabra Campaign Monitor for WordPress. 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-2024-6569/ (Markdown: https://insights.sbomify.com/CVE-2024-6569/index.md)
```

## Sources

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

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