{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-4394 exists.","fix":"No fix has been published for CVE-2021-4394 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-4394 is a medium-severity vulnerability in richardgabriel Locations, published on 1 Jul 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-2021-4394 and fix it if it is affected.\n\nWhat it is: CVE-2021-4394 is a medium-severity vulnerability in richardgabriel Locations, published on 1 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-4394 exists.\n\nAffected product: richardgabriel Locations. 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-2021-4394/ (Markdown: https://insights.sbomify.com/CVE-2021-4394/index.md)","id":"CVE-2021-4394","markdown":"https://insights.sbomify.com/CVE-2021-4394/index.md","name":"CVE-2021-4394","record":{"aliases":["GHSA-gp2m-p45c-8rv4"],"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 trick administrators into modifying custom field metadata via forged requests in the Locations WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"locations","vendor":"goldplugins"}],"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:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Locations plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.2.1. This is due to missing or incorrect nonce validation on the saveCustomFields() function. This makes it possible for unauthenticated attackers to update custom field meta data 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":"weaponised"},"has_fix":null,"headline":"Locations \u003c= 3.2.1 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4394","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":0,"n_references":9,"next":{"headline":"Abandoned Cart Recovery for WooCommerce \u003c= 1.0.4 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4395"},"packages":[],"prev":{"headline":"eCommerce Product Catalog Plugin for WordPress \u003c= 3.0.17 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4393"},"products":["Locations"],"published":"2023-07-01","related":[{"cvss_score":6.5,"headline":"WordPress Locations Plugin \u003c= 4.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-41797","kev_date_added":null,"published":"2023-10-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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["richardgabriel"]},"summary":"Unauthenticated attackers can trick administrators into modifying custom field metadata via forged requests in the Locations WordPress plugin.","url":"https://insights.sbomify.com/CVE-2021-4394/"}