WP Gravity Forms Keap/Infusionsoft Vulnerability (Medium) – CVE-202…

WP Gravity Forms Keap/Infusionsoft Vulnerability (Medium) – CVE-202…

by | Feb 25, 2026 | Plugins

Attack Vectors

WP Gravity Forms Keap/Infusionsoft (slug: gf-infusionsoft) is affected by an Open Redirect vulnerability in versions <= 1.2.6 (Severity: Medium, CVSS 4.3; CVE-2025-58006). The issue occurs when a redirect URL can be supplied without sufficient validation.

From a practical standpoint, an unauthenticated attacker can attempt to redirect a user to an attacker-controlled website if they can successfully trick the user into clicking a link or performing a specific action (this aligns with the “User Interaction” component in the CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N).

For marketing and business teams, the most common delivery methods are typically phishing-style tactics (for example, links embedded in emails, ads, social posts, or partner communications) that appear to originate from a trusted brand domain but ultimately redirect to a malicious destination.

Security Weakness

The core weakness is insufficient validation of a redirect URL parameter. When an application/plugin accepts a user-controllable URL and redirects a browser to it without strict checks (such as enforcing an allowlist of trusted destinations), it can become a reliable tool for attackers to “bounce” users from a trusted site to an untrusted one.

This vulnerability affects all versions up to and including 1.2.6 of the WP Gravity Forms Keap/Infusionsoft plugin. Wordfence’s advisory is the primary referenced source for the issue details (Wordfence vulnerability record).

Remediation: Update the plugin to version 1.2.7 or newer, which contains the patch.

Technical or Business Impacts

While an open redirect does not typically “hack” the server directly, it can create significant brand, fraud, and compliance risk because it helps attackers exploit user trust in your domain. This can be especially damaging for organizations running campaigns that drive high traffic through forms and landing pages.

Business impacts may include: increased success rates of phishing and credential theft campaigns using your brand’s reputation; customer complaints and trust erosion after users are redirected to scams; and potential impacts to marketing performance if ad platforms or email providers flag your domain as risky due to abuse patterns.

Operational and governance impacts can include incident response costs (triage, communications, takedown efforts), escalations with Legal/Compliance when customers report fraud, and reputational damage that affects pipeline and renewals. For regulated organizations, even if the vulnerability does not directly expose data (CVSS indicates C:N), downstream phishing enabled by brand-trust redirects can still create reportable security events depending on what happens to users after the redirect.

Similar Attacks

Open redirect weaknesses are widely used in real-world phishing because they let attackers start with a trusted URL and then forward victims to a malicious site. Here are a few credible references and examples of how open redirects are abused:

CISA Alert AA20-073A: Malicious Cyber Actors Exploit Publicly Available Content Management Systems (high-level guidance that includes common web application abuse patterns used for phishing and compromise).

OWASP: Unvalidated Redirects and Forwards (industry-recognized explanation of how attackers leverage open redirects to increase credibility and conversion in phishing flows).

Vantage Vulnerability (Medium) – CVE-2026-5070

Attack Vectors CVE-2026-5070 is a Medium severity vulnerability (CVSS 6.4) affecting the Vantage WordPress theme (slug: vantage) in versions up to and including 1.20.32. It enables authenticated users with Contributor access or higher to inject malicious script into a...

WP Docs Vulnerability (Medium) – CVE-2026-3878

Attack Vectors CVE-2026-3878 is a Medium severity Stored Cross-Site Scripting (XSS) vulnerability (CVSS 6.4) affecting the WP Docs WordPress plugin (wp-docs) in versions 2.2.9 and below. The issue is exploitable by an authenticated user with Subscriber-level access or...

WPFore Subscribers