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-49917: Server-Side Request Forgery (SSRF) in Icegram Icegram Express Pro

0
Medium
VulnerabilityCVE-2025-49917cvecve-2025-49917
Published: Wed Oct 22 2025 (10/22/2025, 14:32:12 UTC)
Source: CVE Database V5
Vendor/Project: Icegram
Product: Icegram Express Pro

Description

Server-Side Request Forgery (SSRF) vulnerability in Icegram Icegram Express Pro email-subscribers-premium allows Server Side Request Forgery.This issue affects Icegram Express Pro: from n/a through <= 5.9.5.

AI-Powered Analysis

AILast updated: 10/22/2025, 15:14:03 UTC

Technical Analysis

CVE-2025-49917 identifies a Server-Side Request Forgery (SSRF) vulnerability in the Icegram Express Pro plugin, specifically affecting versions up to 5.9.5. Icegram Express Pro is a WordPress plugin used primarily for managing email subscriptions and marketing campaigns. SSRF vulnerabilities occur when an attacker can manipulate a server-side application to send crafted HTTP requests to arbitrary domains, including internal or protected network resources that are otherwise inaccessible externally. This vulnerability arises from insufficient validation or sanitization of user-supplied URLs or request parameters within the plugin's email-subscribers-premium component. Exploiting this flaw, an attacker could coerce the server to perform unauthorized requests, potentially accessing internal services, metadata endpoints, or sensitive information stored behind firewalls. Although no public exploits are currently known, the risk remains significant due to the common use of this plugin in WordPress environments and the typical exposure of internal networks to SSRF attacks. The vulnerability affects all versions up to and including 5.9.5, with no patch currently linked, indicating that users must remain vigilant. The lack of a CVSS score suggests the vulnerability is newly disclosed, and severity assessment must consider the potential for internal network reconnaissance, data leakage, or pivoting attacks. The attacker does not require authentication or user interaction, increasing the risk profile. The vulnerability's exploitation could compromise confidentiality and integrity, and potentially availability if leveraged for denial-of-service conditions on internal resources.

Potential Impact

For European organizations, this SSRF vulnerability poses a significant risk, especially for those relying on Icegram Express Pro for email marketing and subscriber management on WordPress platforms. Exploitation could allow attackers to bypass perimeter defenses and access internal network resources, such as intranet services, cloud metadata APIs, or database management interfaces, leading to data breaches or further lateral movement within the network. Confidential customer data, internal configuration details, or sensitive business information could be exposed or manipulated. The impact is heightened for organizations with complex internal networks or those using cloud infrastructure where SSRF can be used to access metadata services and escalate privileges. Additionally, compromised marketing platforms could be used to distribute phishing or malware campaigns, amplifying the threat. The absence of known exploits provides a window for mitigation, but the widespread use of WordPress and related plugins in Europe increases the potential attack surface. Disruption of email marketing services could also affect business continuity and customer engagement.

Mitigation Recommendations

1. Monitor official Icegram channels and Patchstack for the release of security patches addressing CVE-2025-49917 and apply them immediately upon availability. 2. In the interim, restrict outbound HTTP requests from the web server hosting Icegram Express Pro using firewall rules or web application firewalls (WAF) to only trusted destinations, preventing unauthorized SSRF exploitation. 3. Implement network segmentation to isolate internal services and sensitive endpoints from the web server environment. 4. Employ input validation and sanitization at the application level where possible, or disable vulnerable plugin features if feasible. 5. Conduct regular vulnerability scans and penetration testing focused on SSRF vectors in WordPress environments. 6. Monitor server logs and network traffic for unusual outbound requests or patterns indicative of SSRF exploitation attempts. 7. Educate IT and security teams about SSRF risks and detection techniques. 8. Consider deploying runtime application self-protection (RASP) or enhanced WAF rules that can detect and block SSRF payloads targeting the plugin.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-06-11T16:06:59.982Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68f8efeb04677bbd794397f4

Added to database: 10/22/2025, 2:53:31 PM

Last enriched: 10/22/2025, 3:14:03 PM

Last updated: 10/29/2025, 6:59:02 AM

Views: 7

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