Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running PDF for Contact Form 7 ≤7.1.0
-
DeliverySend request with ../ traversal in path parameter
-
ExploitBypass directory restriction in file handler
-
ExecutionServer returns arbitrary file (e.g., wp-config.php)
-
ImpactExfiltrate credentials and secret keys
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Target must run the 'PDF for Contact Form 7' (pdf-for-contact-form-7) WordPress plugin at version 7.1.0 or earlier; the attacker reaches the plugin's PDF file-download/handler endpoint and supplies directory-traversal input in a path/filename parameter to read files outside the intended directory. The supplied CVSS vector indicates no authentication, user interaction, or special configuration is required (PR:N/UI:N), so default installations of the affected plugin versions are exposed. Limiting factors: exploitation depends on the vulnerable plugin being installed and activated (not WordPress core), impact is confined to reading files the web server account can access (confidentiality only - no write or code execution), and if the vendor advisory reveals an authentication or form-submission prerequisite not reflected in the vector, the realistic attack surface is narrower than PR:N suggests. |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) describes a remotely reachable, low-complexity, unauthenticated path traversal with high confidentiality impact and no integrity or availability impact - consistent with the Patchstack reference title 'arbitrary file download vulnerability.' No EPSS score, CISA KEV listing, POC flag, or SSVC decision data was supplied in the input, so exploitation probability and automatability cannot be quantified from the provided signals; there is no public exploit identified at time of analysis. The risk profile is therefore a classic information-disclosure flaw: serious because it can be triggered remotely without credentials and can expose arbitrary server files (e.g., wp-config.php with database credentials and secret keys), but its real-world priority is tempered by a confidentiality-only impact (no code execution or data modification) and by the fact that it affects a specific Contact Form 7 add-on rather than a ubiquitous platform. One caveat to verify: Patchstack-sourced WordPress 'arbitrary file download' issues in form add-ons often require reaching an authenticated or form-submission-gated download endpoint, yet the supplied vector asserts PR:N - if the vendor advisory indicates any privilege or form-interaction prerequisite, the true exploitability is lower than PR:N implies, so confirm the auth precondition against the Patchstack advisory before treating this as fully unauthenticated. |
| Exploit ScenarioDerived | A remote attacker sends a crafted request to the plugin's PDF generation/download handler containing directory-traversal sequences (e.g., ../../) in a filename or path parameter, causing the server to return a file outside the intended directory. By retrieving wp-config.php or other sensitive files, the attacker harvests database credentials and WordPress secret keys for follow-on compromise. No public exploit code was identified in the provided data, but the low attack complexity and network vector make reliable exploitation straightforward once the vulnerable parameter is located. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Unauthenticated remote attackers can read arbitrary files from the underlying web server by exploiting a path traversal flaw in the WordPress plugin PDF for Contact Form 7 (slug pdf-for-contact-form-7) affecting all versions through 7.1.0. Supplying crafted directory-traversal input to the plugin's PDF file-handling/download path lets an attacker escape the intended directory and retrieve files readable by the web server account, a high confidentiality impact with no integrity or availability effect (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N). No public exploit code, CISA KEV listing, or EPSS score was identified in the supplied intelligence, so exploitation has not been confirmed as active and the practical attack surface depends on the plugin being installed and activated; note that WordPress core does not ship this plugin, so exposure is limited to sites running it.
RemediationAI
No fixed plugin version is identified in the supplied data, so treat this as unpatched at time of analysis and verify the current release in the WordPress.org plugin repository and the add-ons.org vendor site before assuming an update addresses it; the authoritative tracking entry is the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/pdf-for-contact-form-7/vulnerability/wordpress-pdf-for-contact-form-7-plugin-7-1-0-arbitrary-file-download-vulnerability?_s_id=cve. Until a patched version is confirmed and deployed, the most reliable compensating control is to deactivate and remove the PDF for Contact Form 7 plugin on sites that do not require it, accepting that PDF generation for Contact Form 7 submissions will stop working; sites that must keep it should restrict network access to the plugin's PDF download/handler endpoint (for example by blocking or IP-limiting the relevant admin-ajax.php action, REST route, or direct plugin PHP path via the web server or a reverse proxy), with the trade-off that legitimate front-end PDF retrieval may break for remote users. Additional hardening includes deploying WAF rules that reject traversal encodings (../, ..\, %2e%2e%2f, %252e%252e%252f, and similar) in path/filename parameters on requests reaching this plugin, though such rules are bypassable with novel encodings and require ongoing tuning; enabling PHP open_basedir and running the web server/PHP-FPM under a least-privilege account with restricted filesystem permissions limits how much data a successful traversal can expose, at the cost of possible false failures in plugins that legitimately read files outside the document root. Because the assessed impact is confidentiality-only and no authentication is required per the CVSS vector, prioritize inventorying which sites still run this plugin and confirming the web server account cannot read wp-config.php backups, database dumps, or other sensitive files it does not strictly need.
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 issue is a CWE-22 improper limitation of a pathname to a restricted directory (path traversal) in the add-ons.org 'PDF for Contact Form 7' WordPress plugin, whose CPE is cpe:2.3:a:add-ons.org:pdf_for_contact_form_7:*:*:*:*:*:*:*:* (version wildcarded, with the vendor advisory scoping the impact to releases through 7.1.0). The plugin generates and serves PDF output for Contact Form 7 submissions; the vulnerable code passes a user-controllable path or filename value into a file access routine without adequately normalizing and constraining it, so sequences such as ../ can escape the intended plugin/upload directory. Because the flaw is in PHP-side file handling rather than in WordPress core, its reach is bounded by the privileges of the PHP/web server process - an attacker gains read-only access to files that account can reach, including potentially wp-config.php and other sensitive local files, but cannot write files or execute code through this vector alone. The supplied CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N indicates the path is network reachable with low complexity and explicitly requires no authentication (PR:N) and no user interaction (UI:N), consistent with the referenced Patchstack advisory title describing an 'arbitrary file download' vulnerability. The independent assessment cautions that if the vendor's advisory reveals an additional prerequisite such as a valid form submission or a capability check not reflected in the vector, the real-world attack surface may be narrower than PR:N implies.
Know when Pdf For 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:U/C:H/I:N/A:N
Remotely reachable traversal with no stated credential or interaction requirement (AV:N/AC:L/PR:N/UI:N); arbitrary file read yields high confidentiality impact only, with no integrity or availability effect.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in add-ons.org PDF for Contact Form 7 pdf-for-contact-form-7 allows Path Traversal.This issue affects PDF for Contact Form 7: from n/a through 7.1.0.
Executive ViewAI
Organizations using the PDF for Contact Form 7 WordPress plugin (versions through 7.1.0) are exposed to unauthenticated file disclosure that could reveal sensitive server files such as configuration and credential material. Because the plugin is third-party and no vendor patch is available, any site running it should be treated as at risk until mitigated or disabled. Leadership should prioritize rapid inventory and containment for affected web properties, as data exposure could affect customer trust, regulatory obligations, and downstream system security.
No vendor-released patch identified at time of analysis. Interim mitigations include deactivating or removing the pdf-for-contact-form-7 plugin, applying WAF virtual patching for path traversal, restricting web server file permissions to least privilege, disabling directory listing, monitoring file access logs, and isolating affected WordPress sites.
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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-95627
GHSA-m86j-fm38-cxr2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB