Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64272: Exposure of Sensitive System Information to an Unauthorized Control Sphere in GetResponse Email marketing for WordPress by GetResponse Official

0
Medium
VulnerabilityCVE-2025-64272cvecve-2025-64272
Published: Thu Dec 18 2025 (12/18/2025, 07:22:15 UTC)
Source: CVE Database V5
Vendor/Project: GetResponse
Product: Email marketing for WordPress by GetResponse Official

Description

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in GetResponse Email marketing for WordPress by GetResponse Official getresponse-official allows Retrieve Embedded Sensitive Data.This issue affects Email marketing for WordPress by GetResponse Official: from n/a through <= 1.5.3.

AI-Powered Analysis

AILast updated: 12/18/2025, 08:12:10 UTC

Technical Analysis

CVE-2025-64272 is a security vulnerability identified in the GetResponse Email marketing plugin for WordPress, specifically affecting versions up to 1.5.3. The vulnerability allows unauthorized actors to access sensitive system information embedded within the plugin, which should normally be restricted to authorized users or internal processes. This exposure occurs due to improper access control mechanisms within the plugin's code, enabling retrieval of data that could include configuration details, API keys, or other sensitive metadata. Such information leakage can facilitate further attacks, including targeted phishing, privilege escalation, or exploitation of other vulnerabilities by providing attackers with critical reconnaissance data. The vulnerability does not require user authentication, making it easier for remote attackers to exploit. Although no public exploits have been reported yet, the risk remains significant given the plugin's widespread use in WordPress-based marketing environments. The lack of a CVSS score indicates the need for a manual severity assessment based on the nature of the vulnerability and its potential impact. The vulnerability was reserved in late October 2025 and published in December 2025, but no patch links are currently available, suggesting that users should monitor for updates from GetResponse or consider temporary mitigations.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the confidentiality of sensitive marketing and system data. Exposure of such information can lead to unauthorized access to customer data, marketing strategies, or internal configurations, potentially resulting in data breaches and reputational damage. Organizations subject to GDPR and other data protection regulations could face compliance violations and associated penalties if sensitive personal data is compromised. The ease of exploitation without authentication increases the likelihood of attacks, especially from opportunistic threat actors scanning for vulnerable WordPress plugins. Additionally, attackers gaining system information could leverage it to launch more sophisticated attacks, including lateral movement within networks or targeted phishing campaigns. The impact on availability and integrity is less direct but could follow from subsequent exploitation steps. Overall, the vulnerability undermines trust in the affected marketing infrastructure and could disrupt business operations reliant on email marketing campaigns.

Mitigation Recommendations

1. Monitor GetResponse official channels for security patches addressing CVE-2025-64272 and apply updates immediately upon release. 2. Until a patch is available, restrict access to the WordPress admin interface and plugin endpoints using web application firewalls (WAFs) or IP whitelisting to limit exposure. 3. Review and harden WordPress installation permissions and configurations to minimize unnecessary data exposure. 4. Conduct regular audits of plugin usage and remove or replace plugins that are no longer maintained or have known vulnerabilities. 5. Implement network segmentation to isolate marketing systems from critical infrastructure to limit lateral movement in case of compromise. 6. Educate staff on recognizing phishing attempts that could leverage information obtained through this vulnerability. 7. Employ intrusion detection systems to monitor for unusual access patterns targeting the plugin or WordPress environment. 8. Backup critical data regularly and verify restoration procedures to mitigate potential downstream impacts.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-10-29T03:08:27.752Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6943b0544eb3efac36700ad0

Added to database: 12/18/2025, 7:42:12 AM

Last enriched: 12/18/2025, 8:12:10 AM

Last updated: 12/19/2025, 10:45:54 AM

Views: 13

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats