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: 11/13/2025, 11:06:50 UTC

Technical Analysis

CVE-2025-49917 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Icegram Express Pro plugin, specifically affecting versions up to and including 5.9.5. SSRF vulnerabilities occur when an attacker can manipulate a server to send crafted requests to unintended locations, often internal network resources or external systems, bypassing network access controls. In this case, the vulnerability exists within the email-subscribers-premium component of Icegram Express Pro, which is commonly used for managing email subscriptions and campaigns on WordPress sites. The vulnerability requires the attacker to have high privileges on the system, meaning they must already be authenticated with elevated rights, which limits the attack surface to insiders or compromised accounts. The CVSS vector indicates network attack vector (AV:N), high attack complexity (AC:H), high privileges required (PR:H), no user interaction (UI:N), and a scope change (S:C), with low confidentiality and integrity impact (C:L/I:L) and no availability impact (A:N). This means the attacker can cause the server to make unauthorized requests, potentially accessing sensitive internal services or metadata endpoints, which could lead to information disclosure or facilitate further attacks such as lateral movement or privilege escalation. No public exploits or patches are currently known, but the vulnerability has been published and reserved since mid-2025. The plugin is widely used in WordPress environments, which are prevalent in many European organizations for marketing and communication purposes.

Potential Impact

For European organizations, the SSRF vulnerability in Icegram Express Pro poses a moderate risk. If exploited, it could allow attackers with high privileges to access internal network resources that are otherwise inaccessible, potentially exposing sensitive data such as internal APIs, cloud metadata services, or administrative interfaces. This could lead to further compromise, including data breaches or lateral movement within the network. Organizations relying heavily on WordPress and Icegram for customer communications and email marketing may face disruption or reputational damage if sensitive subscriber data is exposed. The requirement for high privileges reduces the likelihood of external attackers exploiting this vulnerability directly, but insider threats or compromised administrator accounts increase the risk. Given the widespread use of WordPress and the plugin in Europe, especially in countries with large digital marketing sectors, the impact could be significant if not addressed.

Mitigation Recommendations

1. Immediately audit and restrict administrative access to WordPress installations using Icegram Express Pro to minimize the risk of privilege abuse. 2. Monitor server logs and network traffic for unusual outbound requests originating from the plugin or web server, which may indicate exploitation attempts. 3. Implement network segmentation and firewall rules to limit the server's ability to make arbitrary outbound requests, especially to internal services and metadata endpoints. 4. Disable or remove the email-subscribers-premium component if not essential, reducing the attack surface. 5. Stay alert for official patches or updates from Icegram and apply them promptly once available. 6. Conduct regular security assessments and penetration tests focusing on SSRF and related vulnerabilities within WordPress environments. 7. Employ Web Application Firewalls (WAFs) with rules designed to detect and block SSRF attack patterns targeting the plugin. 8. Educate administrators on the risks of SSRF and the importance of safeguarding privileged accounts.

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: 11/13/2025, 11:06:50 AM

Last updated: 12/14/2025, 8:33:50 AM

Views: 29

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