{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3561 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3561 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3561 is a high-severity SQL injection vulnerability in mgibbs189 Custom Field Suite, published on 20 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3561 and fix it if it is affected.\n\nWhat it is: CVE-2024-3561 is a high-severity SQL injection vulnerability in mgibbs189 Custom Field Suite, published on 20 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-3561 in the wild and no public exploit code.\n\nAffected product: mgibbs189 Custom Field Suite. 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-3561/ (Markdown: https://insights.sbomify.com/CVE-2024-3561/index.md)","id":"CVE-2024-3561","markdown":"https://insights.sbomify.com/CVE-2024-3561/index.md","name":"CVE-2024-3561","record":{"aliases":["GHSA-vr8g-vr45-38w8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can exploit SQL injection in Custom Field Suite to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"custom_field_suite","vendor":"custom_field_suite_project"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The Custom Field Suite plugin for WordPress is vulnerable to SQL Injection via the the 'Term' custom field in all versions up to, and including, 2.6.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Custom Field Suite \u003c= 2.6.7 - Authenticated (Contributor+) SQL Injection via Term Custom Field","id":"CVE-2024-3561","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Custom Field Suite \u003c= 2.6.7 - Authenticated (Contributor+) PHP Code Injection via Loop Custom Field","id":"CVE-2024-3562"},"packages":[],"prev":{"headline":"LearnPress – WordPress LMS Plugin \u003c= 4.2.6.4 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-3560"},"products":["Custom Field Suite"],"published":"2024-06-20","related":[{"cvss_score":8.8,"headline":"Custom Field Suite \u003c= 2.6.7 - Authenticated (Contributor+) PHP Code Injection via Loop Custom Field","id":"CVE-2024-3562","kev_date_added":null,"published":"2024-06-20"},{"cvss_score":6.4,"headline":"Custom Field Suite \u003c= 2.6.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via cfs[post_title]","id":"CVE-2024-3558","kev_date_added":null,"published":"2024-06-20"},{"cvss_score":6.4,"headline":"Custom Field Suite \u003c= 2.6.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via cfs[post_content]","id":"CVE-2024-3559","kev_date_added":null,"published":"2024-06-12"},{"cvss_score":5.9,"headline":"WordPress Custom Field Suite Plugin \u003c= 2.6.2.1 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-32515","kev_date_added":null,"published":"2023-05-18"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2019-11871","kev_date_added":null,"published":"2019-05-10"},{"cvss_score":4.4,"headline":"Custom Field Suite \u003c= 2.6.5 - Authenticated (Admin+) Stored Cross-Site Scripting","id":"CVE-2024-3068","kev_date_added":null,"published":"2024-05-09"}],"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":["mgibbs189"]},"summary":"Authenticated contributors can exploit SQL injection in Custom Field Suite to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2024-3561/"}