CVE-2025-30795

Automation By Autonami <= 3.5.1 - Open Redirect

2025-03-27 00:00
Le Ngoc Anh

Strategic Overview

Status
Patched in 3.5.2
Affected Version
<= 3.5.1
CVSS
7.2High
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2025-30795
View all FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce vulnerabilities

At a glance

CVE-2025-30795 is a high-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the FunnelKit Automations WordPress plugin, affecting versions <= 3.5.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.5.2; sites on affected versions should update now. Disclosed March 2025, reported by Le Ngoc Anh.

Vulnerability Overview

The FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 3.5.1. This is due to insufficient validation on a redirect url supplied. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in FunnelKit Automations <= 3.5.1 takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For FunnelKit Automations the fix is 3.5.2: builds <= 3.5.1 are affected, anything from 3.5.2 onward is not.

Remediation

Update to version 3.5.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to FunnelKit Automations: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: FunnelKit Automations 3.5.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C