6 matches found
CVE-2025-2883 Accept SagePay Payments Using Contact Form 7 <= 2.0 - Unauthenticated Information Exposure
The Accept SagePay Payments Using Contact Form 7 plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.0 through the publicly accessible phpinfo.php script. This makes it possible for unauthenticated attackers to view potentially sensitive...
CVE-2025-2883
CVE-2025-2883 affects the WordPress plugin Accept SagePay Payments Using Contact Form 7. Exposed phpinfo.php in all versions up to 2.0 can leak potentially sensitive information publicly; exploitation would be unauthenticated. Wordfence lists this CVE as patched in its monitoring, and connected s...
CVE-2025-2883 Accept SagePay Payments Using Contact Form 7 <= 2.0 - Unauthenticated Information Exposure
The Accept SagePay Payments Using Contact Form 7 plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.0 through the publicly accessible phpinfo.php script. This makes it possible for unauthenticated attackers to view potentially sensitive...
PT-2025-15415
Name of the Vulnerable Software and Affected Versions: Accept SagePay Payments Using Contact Form 7 plugin for WordPress versions 2.0 and earlier Description: The issue allows unauthenticated attackers to view potentially sensitive information contained in an exposed file through the publicly...
WordPress plugin: Vulnerability in Accepting SagePay Payments Using Contact Form 7 leads to information leakage
WordPress and WordPress plugin are products of the WordPress Foundation, a blogging platform developed in PHP. The platform supports personal blog sites on PHP and MySQL servers.WordPress plugin is an application plugin. An information disclosure vulnerability exists in WordPress plugin Accept...
CVE-2025-2883: Exposure of Sensitive Information to an Unauthorized Actor
The Accept SagePay Payments Using Contact Form 7 plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.0 through the publicly accessible phpinfo.php script. This makes it possible for unauthenticated attackers to view potentially sensitive...