CVE-2024-3597: The Export WP Page to Static HTML/CSS plugin for WordPress is vulnerable to Open Redirect in all versions up t

Q: How do I fix CVE-2024-3597?

export wp page to static html\/css: upgrade to newer than 2.2.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-3597 being exploited?

CVE-2024-3597 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-3597 affect?

CVE-2024-3597 affects export wp page to static html\/css. Severity is high (CVSS 7.1). 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 paramete

Routine

HIGH 7.1UPGRADE

CVE-2024-3597 is a high-severity flaw (CVSS 7.1) affecting export wp page to static html\/css. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-601
Published	2024-06-20
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: myrecorp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-20 02:15 UTCPublished CVE record published
2026-06-17 07:44 UTCUpdated Record last modified

myrecorp export wp page to static html\/css UPGRADE

Affected: <= 2.2.2

Fixed in: newer than 2.2.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy export-wp-page-to-static-htmlcss || rpm -q export-wp-page-to-static-htmlcss || export-wp-page-to-static-htmlcss --version

2. UPGRADE to newer than 2.2.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade export-wp-page-to-static-htmlcss

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade export-wp-page-to-static-htmlcss

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-3597?

export wp page to static html\/css: upgrade to newer than 2.2.2. Exact commands for each OS are on this page.

Is CVE-2024-3597 being exploited?

CVE-2024-3597 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-3597 affect?

CVE-2024-3597 affects export wp page to static html\/css. Severity is high (CVSS 7.1). 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 paramete

How urgent is CVE-2024-3597?

Priority 31/100. High severity

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-6369 MEDIUM 5.4 UPGRADE The Export WP Page to Static HTML/CSS plugin for WordPress is vulnerable to unauthorized access of data and mo
CVE-2023-31077 MEDIUM 4.3 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in ReCorp Export WP Page to Static HTML/CSS plugin <= 2.1.9 ve

References

← Back to latest CVEs