{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2376 exists.","fix":"No fix has been published for CVE-2024-2376 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-2376 is a high-severity vulnerability in Unknown WPQA Builder, published on 3 Jul 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-2376 and fix it if it is affected.\n\nWhat it is: CVE-2024-2376 is a high-severity vulnerability in Unknown WPQA Builder, published on 3 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2376 exists.\n\nAffected product: Unknown WPQA Builder. 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-2376/ (Markdown: https://insights.sbomify.com/CVE-2024-2376/index.md)","id":"CVE-2024-2376","markdown":"https://insights.sbomify.com/CVE-2024-2376/index.md","name":"CVE-2024-2376","record":{"aliases":["GHSA-h3q5-gjcc-wrm3"],"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 logged-in users to follow or unfollow categories and tags via CSRF, requiring an upgrade to the WPQA Builder plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wpqa_builder","vendor":"2code"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","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-352","name":"Cross-Site Request Forgery"}],"description":"The WPQA Builder WordPress plugin before 6.1.1 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks","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":"WPQA \u003c 6.1.1 - Arbitrary Category and Tag Follow/Unfollow via CSRF","id":"CVE-2024-2376","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Misconfiguration in SDM600","id":"CVE-2024-2377"},"packages":[],"prev":{"headline":"WPQA \u003c 6.1.1 - Contributor+ Stored XSS","id":"CVE-2024-2375"},"products":["WPQA Builder"],"published":"2024-07-03","related":[{"cvss_score":8.8,"headline":"WPQA \u003c 5.9 - Follow/Unfollow via CSRF","id":"CVE-2022-3688","kev_date_added":null,"published":"2022-11-21"},{"cvss_score":6.1,"headline":"WPQA \u003c 5.4 - Reflected Cross-Site Scripting","id":"CVE-2022-1597","kev_date_added":null,"published":"2022-06-06"},{"cvss_score":5.9,"headline":"WPQA \u003c 6.1.1 - Contributor+ Stored XSS","id":"CVE-2024-2375","kev_date_added":null,"published":"2024-07-03"},{"cvss_score":5.4,"headline":"WPQA \u003c 5.2 - Subscriber+ Stored Cross-Site Scripting via Profile fields","id":"CVE-2022-1051","kev_date_added":null,"published":"2022-05-16"},{"cvss_score":5.3,"headline":"WPQA \u003c 5.5 - Unauthenticated Private Message Disclosure","id":"CVE-2022-1598","kev_date_added":null,"published":"2022-06-06"},{"cvss_score":4.3,"headline":"WPQA \u003c 5.7 - Subscriber+ Private Message Disclosure via IDOR","id":"CVE-2022-2198","kev_date_added":null,"published":"2022-08-22"}],"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":"2024-08-01","vendors":["Unknown"]},"summary":"Attackers can force logged-in users to follow or unfollow categories and tags via CSRF, requiring an upgrade to the WPQA Builder plugin.","url":"https://insights.sbomify.com/CVE-2024-2376/"}