CVE-2024-3597

Export WP Page to Static HTML/CSS <= 2.2.2 - Open Redirect

2024-06-19 12:17
Krzysztof Zając

Strategic Overview

Status
Patched in 2.2.3
Affected Plugin
Export WordPress Pages to Static HTML & PDF — Static Site Export
Affected Version
<= 2.2.2
CVSS
7.1High
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2024-3597
View all Export WordPress Pages to Static HTML & PDF — Static Site Export vulnerabilities

At a glance

CVE-2024-3597 is a high-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Export WordPress Pages to Static HTML & PDF WordPress plugin, affecting versions <= 2.2.2. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.3; sites on affected versions should update now. Disclosed June 2024, reported by Krzysztof Zając.

Vulnerability Overview

The Export WP Page to Static HTML/CSS plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 2.2.2. This is due to insufficient validation on the redirect url supplied via the rc_exported_zip_file 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')

Reaching this weakness in Export WordPress Pages to Static HTML & PDF <= 2.2.2 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 Export WordPress Pages to Static HTML & PDF the fix is 2.2.3: builds <= 2.2.2 are affected, anything from 2.2.3 onward is not.

Remediation

Update to version 2.2.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Export WordPress Pages to Static HTML & PDF: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Export WordPress Pages to Static HTML & PDF 2.2.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-3597https://www.wordfence.com/threat-intel/vulnerabilities/id/598e2c2e-7dd5-435e-a366-6c7569243f2ahttps://nvd.nist.gov/vuln/detail/CVE-2024-3597

Related records

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