Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public CF7 form on target
-
DeliverySubmit form with internal URL in content
-
ExploitServer-side PDF renderer fetches internal resource
-
ExecutionResponse embedded into generated PDF
-
ImpactAttacker reads PDF to exfiltrate internal data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires only that the target WordPress site runs the 'Generate PDF using Contact Form 7' plugin before version 4.2.2 with a publicly reachable Contact Form 7 form that triggers PDF generation on submission. No authentication, no user interaction, and no special configuration are needed (PR:N/UI:N) - the attacker directly submits crafted form content whose image/URL destination is fetched server-side without restriction. Practical limits: the plugin must be installed and PDF generation must be invoked on submitted content, the fetched internal service must return data that survives rendering into the PDF, and the site must be patched-below-4.2.2; there is no lateral impact beyond information disclosure (I:N/A:N). |
| Impact | This is a genuine, exploitable network SSRF that warrants prioritization above a typical low-CVSS plugin bug because multiple signals align: the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) is fully unauthenticated with low complexity and no user interaction, a public exploit exists (WPScan), and a vendor patch is available. The vendor base score of 5.8 is arguably UNDERSTATED - the vulnerability is a NON-blind SSRF where the internal-resource response is read back through the generated PDF, which functions as an exfiltration channel; that meaningfully increases confidentiality impact beyond the assigned C:L (a case for C:H can be made, pushing my own estimate to ~6.5-7.5). No EPSS score and no KEV listing are provided, so there is no evidence of active in-the-wild exploitation - the risk today is elevated-but-not-emergency: real, unauthenticated, and POC-backed, but not confirmed weaponized at scale. Bottom line: treat as a real priority for internet-facing WordPress sites running this plugin because unauth + POC + response-exfil is a dangerous combination, while noting exploitation status is currently limited to public POC rather than observed attacks. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a Contact Form 7 form whose content references an attacker-chosen internal URL (e.g., a cloud metadata endpoint or an internal admin service); the plugin's PDF renderer fetches that URL server-side and embeds/reflects the response into the generated PDF, which the attacker then reads to exfiltrate internal data. A public POC is available from WPScan, and because the CVSS vector is AV:N/AC:L/PR:N/UI:N the attack requires no authentication, no user interaction, and only a single crafted form submission. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Unauthenticated server-side request forgery (SSRF) in the WordPress plugin 'Generate PDF using Contact Form 7' before version 4.2.2 lets remote attackers force the server to fetch an arbitrary URL - including internal-only resources - and read the fetched content back out of the generated PDF. Exploitation requires only that the site runs the vulnerable plugin and exposes a Contact Form 7 form whose submission triggers PDF generation; no credentials or user interaction are needed (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C, assessed C:H versus the published C:L). A publicly available exploit exists (WPScan), and a vendor fix is available in 4.2.2, so upgrading is the decisive action.
RemediationAI
Apply the vendor fix: upgrade 'Generate PDF using Contact Form 7' to version 4.2.2 or later (Vendor-released patch: 4.2.2), which restores restriction on the destination of the renderer's image fetch; the WPScan advisory at https://wpscan.com/vulnerability/1aa459e4-bd75-49a5-a6de-812375d441e6/ and the EUVD/VulDB entries at https://nvd.nist.gov/vuln/detail/CVE-2026-90984 and https://vuldb.com/vuln/407364 should be used to confirm the fixed build and to drive an inventory check for the plugin across all WordPress instances. If patching must be delayed, the highest-value compensating control is to deactivate the plugin until it can be updated, accepting the loss of PDF-generation functionality; a narrower alternative is to remove or unpublish every Contact Form 7 form that triggers PDF generation (trade-off: legitimate form-to-PDF workflows stop working) while leaving the plugin in place. Because the request originates from the web server itself, also enforce server-side egress filtering to deny outbound HTTP(S) from the WordPress host to loopback (127.0.0.0/8), link-local and cloud metadata (169.254.0.0/16, including 169.254.169.254), and RFC1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), and block DNS resolution of internal names (trade-off: any legitimate integration the site has with internal services will break, and egress rules must be maintained as infrastructure changes). A WAF or reverse-proxy rule that rejects submissions containing internal IP literals or internal hostnames in URL/image fields can add short-term coverage, but it is bypassable via DNS rebinding, URL encoding, and redirect chains, so it must not replace the 4.2.2 upgrade.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic server-side request forgery (CWE-918) rooted in the plugin's PDF rendering pipeline. When a Contact Form 7 submission includes an image/URL reference, the PDF renderer dereferences that destination server-side without validating or allowlisting the host, scheme, or resolved IP. Because the requested target never has to be a public image, an attacker can point it at loopback addresses, link-local cloud metadata endpoints (for example 169.254.169.254), or other internal HTTP services reachable from the WordPress host, and the response body is embedded into the PDF that is returned to the submitter - turning a blind request into a read primitive. The CVSS 3.1 vector carries Scope:Changed (S:C), reflecting that the vulnerable plugin process can reach resources outside its own security authority (the internal network), while impacts are limited to confidentiality (C:L per NVD, assessed C:H because internal responses can be exfiltrated, with I:N/A:N confirming no integrity or availability effect). The single supplied CPE (cpe:2.3:a:unknown:generate_pdf_using_contact_form_7:*:*:*:*:*:*:*:*) is a wildcard, meaning it does not pin specific builds; the reliable version boundary comes from the advisory data (0 through below 4.2.2).
Know when Generate Pdf Using Contact Form 7 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Unauthenticated network SSRF (PR:N/UI:N/AC:L); S:C as the request crosses into internal network boundary; C:H rather than C:L because the response is read back through the PDF (full read), I/A none.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Generate PDF using Contact Form 7 WordPress plugin before 4.2.2 does not restrict the destination of the image fetch its PDF renderer performs on submitted form content, allowing unauthenticated users to make the server request internal resources and read the response back through the generated PDF.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
The Generate PDF using Contact Form 7 plugin for WordPress is vulnerable to Cross-Site Request Forgery to Arbitrary File
The Generate PDF using Contact Form 7 plugin for WordPress is vulnerable to Cross-Site Request Forgery to Arbitrary File
Unrestricted Upload of File with Dangerous Type vulnerability in ZealousWeb Generate PDF using Contact Form 7 generate-p
The Generate PDF WordPress plugin before 3.6 does not sanitise and escape its settings, allowing high privilege users su
Unauthenticated path traversal in ZealousWeb's Generate PDF using Contact Form 7 WordPress plugin, affecting all release
EUVD-2026-82683
GHSA-c3g6-9rgm-rg4m
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB