dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6569

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Campaign Monitor for WordPress plugin is vulnerable to Full Path Disclosure (FPD) due to insufficient restrictions on direct access to /forms/views/admin/create.php combined with PHP's display_errors being enabled. Unauthenticated attackers can retrieve the full server path of the web application, which aids in reconnaissance for subsequent attacks.

MitigationDisable PHP's display_errors setting on production servers and update the plugin to version 2.8.16 or later when a patch becomes available. Consider adding .htaccess rules to prevent direct access to plugin PHP files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Campaign Monitor plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Campaign Monitor' or check /wp-content/plugins/ for a campaign-monitor directory
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Check the installed plugin version
    View the plugin details in WordPress admin plugins list or read the main plugin PHP file header for the Version field
    Affected if Version is lower than 2.8.16 or the version cannot be determined (unpatched)
  3. Check if PHP display_errors is enabled
    Create a PHP info page or check php.ini for 'display_errors = On', or run: php -i | grep display_errors from command line
    Affected if display_errors is set to On (this setting enables the path disclosure)
  4. Verify the vulnerable file exists and is accessible
    Attempt to access /wp-content/plugins/campaign-monitor/forms/views/admin/create.php directly via HTTP request
    Affected if The file is accessible and returns a PHP error revealing the full server path

A user is affected if the Campaign Monitor plugin is installed with a version below 2.8.16 AND PHP's display_errors setting is enabled, allowing unauthenticated path disclosure via the create.php file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable PHP's display_errors setting on production servers and update the plugin to version 2.8.16 or later when a patch becomes available. Consider adding .htaccess rules to prevent direct access to plugin PHP files.

Recommended fix High confidence

Version 2.8.16 or later (upgrade to latest available version)

  1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. Locate the 'Campaign Monitor for WordPress' plugin
  3. Check the current version - if it is 2.8.15 or earlier, an update is available
  4. Click 'Update Now' to upgrade to the latest version
  5. Verify the update completes successfully
  6. Confirm the new version number after updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6569 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data