EUVD-2026-62385
GHSA-4pwf-69q9-4vvg
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-accessible endpoint exposes sensitive data with no authentication, interaction, or complexity required; only confidentiality is impacted.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Lifecycle Timeline
2DescriptionCVE.org
Unauthenticated Sensitive Data Exposure in Pay with Contact Form 7 <= 1.0.4 versions.
AnalysisAI
Unauthenticated sensitive data exposure in the CMSMinds Pay with Contact Form 7 WordPress plugin (versions through 1.0.4) allows remote, unauthenticated attackers to retrieve sensitive information - likely payment-related or personal contact data - without any credentials or user interaction. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) confirms a fully network-accessible attack path requiring zero privileges, yielding high confidentiality impact. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | No special conditions are required beyond the target WordPress site having the Pay with Contact Form 7 plugin (version 1.0.4 or earlier) installed and active. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 7.5 High rating is well-supported by the vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N): the attack requires no authentication, no special configuration, and no user interaction, and yields high confidentiality impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An unauthenticated attacker enumerates a target WordPress site, detects the presence of the Pay with Contact Form 7 plugin (e.g., via plugin-specific asset paths), then sends a crafted HTTP request to the vulnerable endpoint - requiring no credentials or cookies - and receives a response containing sensitive data such as payment transaction records or personal contact submissions. No public exploit code has been identified at time of analysis, but the low complexity of the attack vector makes manual exploitation straightforward. |
| Remediation | The primary remediation is to update the Pay with Contact Form 7 plugin to a version beyond 1.0.4; however, the available reference data does not specify an exact patched version number - administrators should consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/pay-with-contact-form-7/vulnerability/wordpress-pay-with-contact-form-7-plugin-1-0-4-sensitive-data-exposure-vulnerability and the WordPress plugin repository for the latest release. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: identify all WordPress instances running CMSMinds Pay plugin versions 1.0.4 or earlier and disable or remove the plugin; perform forensic review of access logs to detect unauthorized retrieval of payment data. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today