# CVE-2024-3585: Send PDF for Contact Form 7 <= 1.0.2.3 - Missing Authorization

> Unauthenticated attackers can download contact form entries with PDFs due to missing capability checks in the Send PDF for Contact Form 7 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:** 2 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8296-pfrx-5qgf

## What is CVE-2024-3585?

CVE-2024-3585 is a medium-severity missing authorization vulnerability in florent73 Send PDF for Contact Form 7, published on 2 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-3585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3585 is a medium-severity missing authorization vulnerability in florent73 Send PDF for Contact Form 7, published on 2 May 2024. 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-2024-3585 in the wild and no public exploit code.

Affected product: florent73 Send PDF for Contact Form 7. 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-3585/ (Markdown: https://insights.sbomify.com/CVE-2024-3585/index.md)
```

## Sources

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

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