CVE Alert: CVE-2025-10861 – roxnor – Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers
CVE-2025-10861
The Popup builder with Gamification, Multi-Step Popups, Page-Level Targeting, and WooCommerce Triggers plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.1.4. This is due to insufficient validation on the URLs supplied via the URL parameter. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services, as well as conduct network reconnaissance. The vulnerability was partially patched in version 2.1.4.
AI Summary Analysis
Risk verdict
High risk: unauthenticated SSRF in the WordPress plugin could reach internal services; no active exploitation confirmed, but patching should be treated as urgent.
Why this matters
Attacker capability to query internal resources from the application could enable data exposure and reconnaissance, with potential pivot to other internal systems. Business impact includes leakage of sensitive data and possible disruption of services that rely on internal APIs.
Most likely attack path
No user interaction required. An attacker provides a crafted URL in the vulnerable parameter, triggering server-side requests to the target location. This can reach internal networks or other protected resources, enabling automated, credential‑less exploitation of exposed endpoints.
Who is most exposed
Sites hosting this WordPress plugin, especially those on public hosting with WooCommerce deployments and exposed checkout/integration endpoints, are at greatest risk.
Detection ideas
- Outbound requests from the web server to internal IPs or unusual domains.
- Logs showing anomalous URL parameter values or SSRF-like fetches.
- WAF/IDS alerts for SSRF patterns or unexpected fetch destinations.
- spikes in egress to internal services tied to plugin activity.
Mitigation and prioritisation
- Upgrade to a version beyond 2.1.4; if unavailable, disable the fetch/URL parameter feature or the plugin.
- Implement network egress controls and allowlists for internal destinations.
- Apply SSRF-focused WAF rules; validate and constrain URL inputs server-side.
- Harden hosting environment (restrict URL fetch functions where feasible).
- Test in staging before deploy; monitor logs for SSRF indicators after patching.
Support Our Work
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
