CVE-2024-4900

SEOPress <= 7.7.2 - Authenticated (Contributor+) Open Redirect

2024-06-03 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 7.8
Affected Version
<= 7.7.2
CVSS
6.4Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2024-4900
View all SEOPress – AI SEO Plugin & On-site SEO vulnerabilities

At a glance

CVE-2024-4900 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the SEOPress WordPress plugin, affecting versions <= 7.7.2. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 7.8; sites on affected versions should update now. Disclosed June 2024, reported by Dmitrii Ignatyev.

Vulnerability Overview

The SEOPress – On-site SEO plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 7.7.2. This is due to insufficient validation on the social post settings. This makes it possible for an authenticated attacker, with contributor-level access and above, 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 interaction from a victim user.

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

Reaching this weakness in SEOPress <= 7.7.2 takes an account at Contributor level or above. 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 SEOPress the fix is 7.8: builds <= 7.7.2 are affected, anything from 7.8 onward is not.

Remediation

Update to version 7.8, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SEOPress 7.8 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