dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-3585

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-02
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 Send PDF for Contact Form 7 plugin for WordPress is vulnerable to unauthorized access of form submissions due to a missing capability check on the hooks function in all versions up to, and including, 1.0.2.3. This makes it possible for unauthenticated attackers to download information about contact form entries with PDFs.

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 · high confidence

The Send PDF for Contact Form 7 WordPress plugin has a broken access control vulnerability where the hooks function lacks proper capability checks. This allows unauthenticated attackers to directly access form submission endpoints and download PDF attachments containing sensitive contact form data.

MitigationUpdate the plugin to version 1.0.2.4 or later which should include proper authorization checks. If no update is available, implement access controls on the affected hooks function to verify user permissions before allowing PDF downloads.

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. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and check if 'Send PDF for Contact Form 7' appears in the installed plugins list
    Affected if the plugin is present in the environment
  2. Identify the installed version
    In the WordPress plugins list, locate the version number displayed under the 'Send PDF for Contact Form 7' plugin name
    Affected if the version is lower than 1.0.2.4 or the version cannot be determined (missing)
  3. Check if PDF download endpoints are exposed
    Attempt to access common PDF download URLs associated with the plugin, such as URLs containing patterns like '/?cf7sdp_pdf=...' or similar endpoints that serve generated PDF files, without providing any authentication credentials
    Affected if PDF files can be downloaded without requiring login or capability verification
  4. Verify hook accessibility
    Inspect the plugin files (typically in wp-content/plugins/send-pdf-for-contact-form-7/) for hooks functions, specifically checking if the functions handling PDF generation or delivery lack current_user_can() or similar capability checks
    Affected if the hooks functions contain no capability checks before processing form data or serving PDF attachments

The environment is affected if the Send PDF for Contact Form 7 plugin is installed with a version before 1.0.2.4 and the PDF download endpoints are accessible without authentication.

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

Update the plugin to version 1.0.2.4 or later which should include proper authorization checks. If no update is available, implement access controls on the affected hooks function to verify user permissions before allowing PDF downloads.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version higher than 1.0.2.3)

  1. Check the current version of the Send PDF for Contact Form 7 plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate 'Send PDF for Contact Form 7' and note the current version
  4. If the installed version is 1.0.2.3 or below, update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the plugin is functioning correctly with your contact forms
  6. Consider reviewing the plugin's changelog to confirm authorization checks were added

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-3585 — 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-3585 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