{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3597 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3597 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3597 is a high-severity vulnerability in recorp Export WordPress Pages to Static HTML \u0026 PDF — Static Site Export, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-3597 and fix it if it is affected.\n\nWhat it is: CVE-2024-3597 is a high-severity vulnerability in recorp Export WordPress Pages to Static HTML \u0026 PDF — Static Site Export, published on 20 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-3597 in the wild and no public exploit code.\n\nAffected product: recorp Export WordPress Pages to Static HTML \u0026 PDF — Static Site Export. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-3597/ (Markdown: https://insights.sbomify.com/CVE-2024-3597/index.md)","id":"CVE-2024-3597","markdown":"https://insights.sbomify.com/CVE-2024-3597/index.md","name":"CVE-2024-3597","record":{"aliases":["GHSA-jr6w-fhh3-hwv9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can redirect users to malicious sites via insufficient validation in the Export WP Page to Static HTML/CSS plugin.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"export_wp_page_to_static_html\\/css","vendor":"myrecorp"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Export WP Page to Static HTML/CSS \u003c= 2.2.2 - Open Redirect","id":"CVE-2024-3597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"ElementsKit Pro \u003c= 3.6.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'ekit_btn_id'","id":"CVE-2024-3598"},"packages":[],"prev":{"headline":"RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.","id":"CVE-2024-3596"},"products":["Export WordPress Pages to Static HTML \u0026 PDF — Static Site Export"],"published":"2024-06-20","related":[{"cvss_score":5.4,"headline":"Export WP Page to Static HTML/CSS \u003c= 2.1.9 - Missing Authorization via Multiple AJAX Actions","id":"CVE-2023-6369","kev_date_added":null,"published":"2024-01-11"},{"cvss_score":4.3,"headline":"WordPress Export WP Page to Static HTML/CSS Plugin \u003c= 2.1.9 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-31077","kev_date_added":null,"published":"2023-11-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["recorp"]},"summary":"Unauthenticated attackers can redirect users to malicious sites via insufficient validation in the Export WP Page to Static HTML/CSS plugin.","url":"https://insights.sbomify.com/CVE-2024-3597/"}