dbcve.org
Export Wp Page To Static Html\/cssWordPress extension · Myrecorp

CVE-2024-3597

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to after 2.2.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Export WP Page to Static HTML/CSS WordPress plugin versions up to 2.2.2 contains an open redirect vulnerability due to insufficient validation on the redirect URL supplied via the rc_exported_zip_file parameter, allowing unauthenticated attackers to redirect users to arbitrary external sites.

MitigationUpdate the plugin to version 2.2.3 or later which contains proper validation of the redirect URL parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Export Wp Page To Static Html\/cssWordPress extension
Affected:<= 2.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Export WP Page to Static HTML/CSS' or 'Myrecorp Export WP Page To Static HTML/CSS' in the list.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Identify installed version
    In the Plugins list, locate the plugin and check the version number displayed beneath the plugin name. Alternatively, inspect the main plugin file header in wp-content/plugins/ for the Version field.
    Affected if The installed version is 2.2.2 or lower.
  3. Verify vulnerable parameter exposure
    Review web server access logs or proxy logs for requests containing the parameter 'rc_exported_zip_file'. This parameter is used during the export process and accepts a redirect URL value.
    Affected if Requests to the site include the rc_exported_zip_file parameter, especially with untrusted or external URLs.
  4. Test redirect behavior
    If authorized for security testing, send a crafted request to the plugin endpoint with rc_exported_zip_file set to an external domain (e.g., rc_exported_zip_file=https://example.com). Observe whether the response or subsequent request redirects to the supplied external URL.
    Affected if The application redirects to the arbitrary URL supplied in the rc_exported_zip_file parameter without proper validation.

A site is affected if the Export WP Page to Static HTML/CSS plugin is installed with version 2.2.2 or lower and the rc_exported_zip_file parameter is accessible, allowing unauthenticated open redirects to external sites.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.2.2
Interim mitigation

Update the plugin to version 2.2.3 or later which contains proper validation of the redirect URL parameter.

Recommended fix Moderate confidence

Version higher than 2.2.2 (check WordPress Plugin Repository for the latest fixed release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Export WP Page to Static HTML/CSS' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually
  6. 6. Verify the plugin has been updated to a version higher than 2.2.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Export Wp Page To Static Html\/css Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3597 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3597 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data