{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-46805 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-46805 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46805 is a medium-severity vulnerability in Lauri Karisola / WP Trio Conditional Shipping for WooCommerce, published on 1 Mar 2023. 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-2022-46805 and fix it if it is affected.\n\nWhat it is: CVE-2022-46805 is a medium-severity vulnerability in Lauri Karisola / WP Trio Conditional Shipping for WooCommerce, published on 1 Mar 2023. 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-2022-46805 in the wild and no public exploit code.\n\nAffected product: Lauri Karisola / WP Trio Conditional Shipping for WooCommerce. 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-2022-46805/ (Markdown: https://insights.sbomify.com/CVE-2022-46805/index.md)","id":"CVE-2022-46805","markdown":"https://insights.sbomify.com/CVE-2022-46805/index.md","name":"CVE-2022-46805","record":{"aliases":["GHSA-j678-qc3p-928v"],"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":"Attackers can force users to activate or deactivate plugin rulesets via CSRF, requiring an upgrade to the Conditional Shipping for WooCommerce plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"conditional_shipping_for_woocommerce","vendor":"wptrio"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in Lauri Karisola / WP Trio Conditional Shipping for WooCommerce plugin \u003c= 2.3.1 leading to activation/deactivation of plugin rulesets.","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":"WordPress Conditional Payments for WooCommerce Plugin \u003c= 2.3.1 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2022-46805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Cart All In One For WooCommerce Plugin \u003c= 1.1.10 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2022-46806"},"packages":[],"prev":{"headline":"WordPress Export Users Data Distinct Plugin \u003c= 1.3 is vulnerable to CSV Injection","id":"CVE-2022-46804"},"products":["Conditional Shipping for WooCommerce"],"published":"2023-03-01","related":[{"cvss_score":5.4,"headline":"WordPress Conditional Shipping for WooCommerce Plugin \u003c= 2.3.1 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2022-46815","kev_date_added":null,"published":"2023-02-02"}],"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-28","vendors":["Lauri Karisola / WP Trio"]},"summary":"Attackers can force users to activate or deactivate plugin rulesets via CSRF, requiring an upgrade to the Conditional Shipping for WooCommerce plugin.","url":"https://insights.sbomify.com/CVE-2022-46805/"}