{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2594 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2594 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2594 is a high-severity vulnerability in TODO Advanced Custom Fields, published on 22 Aug 2022. 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-2594 and fix it if it is affected.\n\nWhat it is: CVE-2022-2594 is a high-severity vulnerability in TODO Advanced Custom Fields, published on 22 Aug 2022. 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-2594 in the wild and no public exploit code.\n\nAffected product: TODO Advanced Custom Fields. 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-2594/ (Markdown: https://insights.sbomify.com/CVE-2022-2594/index.md)","id":"CVE-2022-2594","markdown":"https://insights.sbomify.com/CVE-2022-2594/index.md","name":"CVE-2022-2594","record":{"aliases":["GHSA-m8hq-2c8m-w6cm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can upload allowed files via frontend forms in Advanced Custom Fields, requiring a specific form configuration.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"advanced_custom_fields","vendor":"advancedcustomfields"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"The Advanced Custom Fields WordPress plugin before 5.12.3, Advanced Custom Fields Pro WordPress plugin before 5.12.3 allows unauthenticated users to upload files allowed in a default WP configuration (so PHP is not possible) if there is a frontend form available. This vulnerability was introduced in the 5.0 rewrite and did not exist prior to that release.","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":"Advanced Custom Fields 5.0-5.12.2 - Unauthenticated File Upload","id":"CVE-2022-2594","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Authorization in kromitgmbh/titra","id":"CVE-2022-2595"},"packages":[],"prev":{"headline":"Better Search and Replace \u003c 1.4.1 - Admin+ SQLi","id":"CVE-2022-2593"},"products":["Advanced Custom Fields","Advanced Custom Fields Pro"],"published":"2022-08-22","related":[{"cvss_score":8.8,"headline":"Advanced Custom Fields - Contributor+ PHP Object Injection","id":"CVE-2023-1196","kev_date_added":null,"published":"2023-05-02"},{"cvss_score":7.5,"headline":"Advanced Custom Fields \u003c 6.3 - Contributor+ Custom Field Access","id":"CVE-2024-4565","kev_date_added":null,"published":"2024-06-20"},{"cvss_score":7.5,"headline":"Missing authorization in Advanced Custom Fields and Advanced Custom Fields Pro","id":"CVE-2021-20865","kev_date_added":null,"published":"2021-12-13"},{"cvss_score":7.1,"headline":"WordPress Advanced Custom Fields / Advanced Custom Fields PRO plugins \u003c= 6.1.5 vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-30777","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":6.6,"headline":"Secure Custom Fields \u003c 6.3.6.3 - Admin+ Remote Code Execution","id":"CVE-2024-9529","kev_date_added":null,"published":"2024-11-15"},{"cvss_score":6.5,"headline":"Missing authorization in Advanced Custom Fields","id":"CVE-2022-23183","kev_date_added":null,"published":"2022-03-31"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["TODO"]},"summary":"Unauthenticated attackers can upload allowed files via frontend forms in Advanced Custom Fields, requiring a specific form configuration.","url":"https://insights.sbomify.com/CVE-2022-2594/"}