Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running Super Forms plugin
-
DeliverySend unauthenticated HTTP request with path traversal payload
-
ExploitRetrieve arbitrary server-readable file (e.g., wp-config.php)
-
ExecutionExtract database credentials and secret keys
-
ImpactAuthenticate to database or escalate to full site compromise
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 | No special conditions are required beyond the target WordPress site having the Super Forms plugin installed, active, and running version 6.3.315 or earlier. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms remote unauthenticated exploitation against default configurations with no user interaction. The plugin does not need to be used or configured in any particular way - its mere presence and activation on the site exposes the vulnerable file download endpoint. Limiting factors: the attacker must be able to reach the WordPress site over HTTP/HTTPS (standard internet access or internal network depending on deployment); exploitation is constrained to files readable by the web server OS user (typically www-data), meaning files with restrictive OS permissions outside the web root may not be accessible. |
| Impact | The CVSS 3.1 base score of 7.5 (High) is driven by AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, which accurately reflects unauthenticated network exploitation with no complexity barrier and significant confidentiality impact. There is no EPSS score provided in the source data, no CISA KEV listing, and no confirmed public proof-of-concept code, which moderates the urgency compared to a KEV-listed vulnerability. However, the attack class (path traversal for file read) is extremely well-understood and trivially weaponizable by any attacker with HTTP access to the WordPress site - the absence of a published PoC does not meaningfully reduce risk. The Patchstack report indicates this was responsibly disclosed, suggesting a vendor patch may be forthcoming or already available. Real-world priority should be HIGH for any organization running Super Forms ≤6.3.315 because exploitation requires no authentication, no user interaction, and yields credentials (wp-config.php) that enable full site compromise as a secondary step. Missing data: no EPSS score, no explicit confirmed fixed version, no indication of whether Patchstack's responsible disclosure resulted in an upstream patch prior to publication. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies a WordPress site running Super Forms ≤6.3.315 via HTTP response headers, page source plugin references, or WordPress plugin enumeration. The attacker sends a crafted HTTP request to the vulnerable file download endpoint with a path parameter containing traversal sequences such as '../../wp-config.php', causing the server to return the WordPress configuration file containing database credentials, authentication secret keys, and API tokens. With those credentials, the attacker can authenticate to the database directly or escalate to full site takeover. No public proof-of-concept has been confirmed, but the technique is standard and requires no specialized tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 24, 2026
Unauthenticated arbitrary file download in the Super Forms WordPress plugin (versions up to and including 6.3.315) exposes any file readable by the web server process to remote attackers without any credentials. The root cause is a path traversal flaw (CWE-22) in a file download endpoint that fails to sanitize user-supplied path parameters, enabling directory traversal sequences to escape the intended file root. No public exploit or CISA KEV listing is confirmed at time of analysis, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates trivial, unauthenticated remote exploitation with no special conditions required on default plugin installations.
RemediationAI
The primary remediation is to upgrade Super Forms beyond version 6.3.315 if a patched release has been issued by the vendor - check the official WordPress plugin repository and the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/super-forms/vulnerability/wordpress-super-forms-plugin-6-3-315-arbitrary-file-download-vulnerability for the confirmed fixed version, as no explicit patched version number is provided in the available data. If no patch is yet available or immediate upgrade is not feasible, the most effective compensating control is to deactivate the Super Forms plugin entirely until a fix is applied, which eliminates the attack surface with no side effect other than losing form functionality. As a secondary control, web application firewall rules can be configured to block requests containing path traversal sequences (../, ..\, %2e%2e%2f) targeting WordPress plugin endpoints, though WAF bypass techniques exist and this should not substitute for patching. Additionally, restricting direct file system access from the web server user to sensitive files (wp-config.php, .env) via OS-level permissions reduces the impact if exploitation occurs.
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 vulnerability is classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory - Path Traversal), a well-understood class of flaw where unsanitized user input containing sequences such as '../' is passed directly to a file system operation. The affected product is the Super Forms WordPress plugin, identified by CPE cpe:2.3:a:super_forms:super_forms:*:*:*:*:*:*:*:* across all versions through 6.3.315. In a typical path traversal scenario within a WordPress plugin, a form-handling or file-serving endpoint accepts a filename or path parameter via HTTP GET/POST, and the server resolves the path without canonicalization or boundary enforcement, allowing traversal into directories such as the WordPress root, system directories, or any path accessible to the web server user (commonly www-data or apache). This can expose wp-config.php (containing database credentials and secret keys), .env files, server configuration files, and private keys.
Know when Super Forms 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
Network-accessible unauthenticated file read endpoint; no authentication, interaction, or special config required; impacts only confidentiality with no write or availability effect.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Arbitrary File Download in Super Forms <= 6.3.315 versions.
Executive ViewAI
Super Forms WordPress plugin versions 6.3.315 and earlier contain an unauthenticated path traversal vulnerability that allows remote attackers to download any file readable by the web server, including configuration files with database credentials and sensitive system data. Organizations using this plugin face immediate data breach risk without requiring attackers to authenticate or exploit complex conditions. The vulnerability affects default plugin installations and exposes critical organizational data with trivial technical barriers to exploitation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable/uninstall the Super Forms plugin if functionality is not critical; (2) Deploy WAF rules to block HTTP requests to known vulnerable download endpoints; (3) Implement reverse proxy authentication requiring valid credentials before plugin access; (4) Restrict file server permissions to prevent web process from reading sensitive files outside intended directories; (5) Monitor web server logs for suspicious file access patterns and path traversal attempts.
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-64796
GHSA-2r89-pxpw-mwf2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB