{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0432 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0432 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0432 is a medium-severity vulnerability in easynolo Ecommerce Fabrick, published on 28 Feb 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-0432 and fix it if it is affected.\n\nWhat it is: CVE-2024-0432 is a medium-severity vulnerability in easynolo Ecommerce Fabrick, published on 28 Feb 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-0432 in the wild and no public exploit code.\n\nAffected product: easynolo Ecommerce Fabrick. 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-0432/ (Markdown: https://insights.sbomify.com/CVE-2024-0432/index.md)","id":"CVE-2024-0432","markdown":"https://insights.sbomify.com/CVE-2024-0432/index.md","name":"CVE-2024-0432","record":{"aliases":["GHSA-5jrc-78c2-4pq8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can delete user card tokens via CSRF by tricking administrators into clicking a link in the Gestpay for WooCommerce plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"gestpay_for_woocommerce","vendor":"fabrick"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Gestpay for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 20221130. This is due to missing or incorrect nonce validation on the 'ajax_delete_card' function. This makes it possible for unauthenticated attackers to delete the default card token for a user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"Gestpay for WooCommerce \u003c= 20221130 - Cross-Site Request Forgery (CSRF) via ajax_delete_card","id":"CVE-2024-0432","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Gestpay for WooCommerce \u003c= 20221130 - Cross-Site Request Forgery (CSRF) via ajax_unset_default_card","id":"CVE-2024-0433"},"packages":[],"prev":{"headline":"Gestpay for WooCommerce \u003c= 20221130 - Cross-Site Request Forgery (CSRF) via ajax_set_default_card","id":"CVE-2024-0431"},"products":["Ecommerce Fabrick"],"published":"2024-02-28","related":[{"cvss_score":4.3,"headline":"Gestpay for WooCommerce \u003c= 20221130 - Cross-Site Request Forgery (CSRF) via ajax_set_default_card","id":"CVE-2024-0431","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":4.3,"headline":"Gestpay for WooCommerce \u003c= 20221130 - Cross-Site Request Forgery (CSRF) via ajax_unset_default_card","id":"CVE-2024-0433","kev_date_added":null,"published":"2024-02-28"}],"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":["easynolo"]},"summary":"Unauthenticated attackers can delete user card tokens via CSRF by tricking administrators into clicking a link in the Gestpay for WooCommerce plugin.","url":"https://insights.sbomify.com/CVE-2024-0432/"}