Construtor de Pop-ups com Gamificação, Pop-ups Multi-Etapas, Segmentação por Página e Gatilhos WooCommerce <= 2.1.4 - Solicitação Forjada do Lado do Servidor Não Autenticada

The SSRF vulnerability in the Popup Builder plugin allows attackers to craft malicious URLs that the plugin will then request. This can be exploited to access internal services that are not directly accessible from the outside world, such as administrative dashboards, databases, or other internal APIs. An attacker could potentially query sensitive information, modify data, or even gain a foothold within the internal network. The lack of authentication requirements means that any user, even without a WordPress account, can trigger these requests. This vulnerability presents a significant risk to WordPress sites utilizing this plugin, especially those with sensitive internal services.

WordPress websites utilizing the Popup Builder plugin, particularly those with sensitive internal services or those running older, unpatched versions (0.0.0 – 2.1.4). Shared hosting environments are also at increased risk, as vulnerabilities in plugins can impact multiple websites on the same server.

• wordpress / plugin: Use wp-cli plugin update to check the installed version. If below 2.1.5, the system is vulnerable. • generic web: Monitor access logs for outbound requests to unusual internal IP addresses or domains originating from the plugin's files (e.g., /wp-content/plugins/popup-builder/). • generic web: Use curl to test for SSRF by attempting to access internal resources through the plugin's URL parameter. Example: curl 'http://your-wordpress-site.com/?popup_url=http://127.0.0.1:8080' • wordpress / plugin: Search plugin files for instances of wpremoteget or similar functions without proper URL validation.

1. 2025-10-24Disclosure

   disclosure

1. Reservado2025-09-22
2. Publicada2025-10-24
3. Modificada2026-04-08
4. EPSS atualizado2026-03-23

The primary mitigation for CVE-2025-10861 is to immediately upgrade the Popup Builder plugin to version 2.1.5 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider implementing a Web Application Firewall (WAF) rule to block requests containing suspicious URLs or patterns indicative of SSRF exploitation. Additionally, review and restrict access to internal services to minimize the potential impact of a successful SSRF attack. Monitor WordPress access logs for unusual outbound requests originating from the plugin.