{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-7419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-7419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-7419 is a high-severity code injection vulnerability in WP All Export Pro, published on 7 Feb 2025. 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-7419 and fix it if it is affected.\n\nWhat it is: CVE-2024-7419 is a high-severity code injection vulnerability in WP All Export Pro, published on 7 Feb 2025. 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-7419 in the wild and no public exploit code.\n\nAffected product: WP All Export Pro. 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-7419/ (Markdown: https://insights.sbomify.com/CVE-2024-7419/index.md)","id":"CVE-2024-7419","markdown":"https://insights.sbomify.com/CVE-2024-7419/index.md","name":"CVE-2024-7419","record":{"aliases":["GHSA-q366-9pf7-w4g2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary PHP code via custom export fields in WP All Export Pro, leading to site compromise.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_all_export","vendor":"soflyy"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The WP ALL Export Pro plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.9.1 via the custom export fields. This is due to the missing input validation and sanitization of user-supplied data. This makes it possible for unauthenticated attackers to inject arbitrary PHP code into form fields that get executed on the server during the export, potentially leading to a complete site compromise. \r\nAs a prerequisite, the custom export field should include fields containing user-supplied data.","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":"WP All Export Pro \u003c= 1.9.1 - Unauthenticated Remote Code Execution via Custom Export Fields","id":"CVE-2024-7419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Insert PHP Code Snippet \u003c= 1.3.6 - Cross-Site Request Forgery to Code Snippet Activate/Deactivate/Deletion","id":"CVE-2024-7420"},"packages":[],"prev":{"headline":"The Post Grid \u003c= 7.7.11 - Authenticated (Contributor+) Information Disclosure","id":"CVE-2024-7418"},"products":["WP All Export Pro"],"published":"2025-02-07","related":[{"cvss_score":8.8,"headline":"WP All Export Pro \u003c 1.7.9 - Authenticated SQLi","id":"CVE-2022-3395","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":7.2,"headline":"WP All Export Pro \u003c 1.7.9 - Authenticated Code Injection","id":"CVE-2022-3394","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":6.8,"headline":"WP All Export Pro \u003c= 1.9.1 - Authenticated (ShopManager+) Arbtirary Options Update","id":"CVE-2024-7425","kev_date_added":null,"published":"2025-02-07"}],"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":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["WP All Import"]},"summary":"Unauthenticated attackers can execute arbitrary PHP code via custom export fields in WP All Export Pro, leading to site compromise.","url":"https://insights.sbomify.com/CVE-2024-7419/"}