CVE-2023-5610

Seraphinite Accelerator <= 2.20.28 - Arbitrary Redirect via 'redir'

2023-10-27 00:00
Erwan LR

Strategic Overview

Status
Patched in 2.20.29
Affected Plugin
Seraphinite Accelerator
Affected Version
<= 2.20.28
CVSS
5.4Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2023-5610
View all Seraphinite Accelerator vulnerabilities

At a glance

CVE-2023-5610 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Seraphinite Accelerator WordPress plugin, affecting versions <= 2.20.28. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.20.29; sites on affected versions should update now. Disclosed October 2023, reported by Erwan LR.

Vulnerability Overview

The Seraphinite Accelerator plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 2.20.28. This is due to insufficient validation on the redirect url supplied via the 'redir' parameter. 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.

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

Seraphinite Accelerator <= 2.20.28 carries this weakness at redir, and reaching it 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 Seraphinite Accelerator the fix is 2.20.29: builds <= 2.20.28 are affected, anything from 2.20.29 onward is not.

Remediation

Update to version 2.20.29, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-5610https://www.wordfence.com/threat-intel/vulnerabilities/id/9d6dd532-008b-4ce9-beca-baf5b3678a0bhttps://nvd.nist.gov/vuln/detail/CVE-2023-5610

Related records

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