{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3343 exists.","fix":"No fix has been published for CVE-2022-3343 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3343 is a low-severity vulnerability in Unknown Discy, published on 9 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-3343 and fix it if it is affected.\n\nWhat it is: CVE-2022-3343 is a low-severity vulnerability in Unknown Discy, published on 9 Jan 2023. Any signed-in user can exploit it over the network, 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-2022-3343 exists.\n\nAffected product: Unknown Discy. 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-3343/ (Markdown: https://insights.sbomify.com/CVE-2022-3343/index.md)","id":"CVE-2022-3343","markdown":"https://insights.sbomify.com/CVE-2022-3343/index.md","name":"CVE-2022-3343","record":{"aliases":["GHSA-v24x-rp9v-pm6r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can inflate user scores by exploiting missing validation in the WPQA Builder plugin's follow functionality.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wpqa_builder","vendor":"2code"}],"cvss":{"score":3.5,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"The WPQA Builder WordPress plugin before 5.9.3 (which is a companion plugin used with Discy and Himer Discy WordPress themes) incorrectly tries to validate that a user already follows another in the wpqa_following_you_ajax action, allowing a user to inflate their score on the site by having another user send repeated follow actions to them.","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 5.9.3 - Missing validation lead to functionality abuse","id":"CVE-2022-3343","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Linux kernel","id":"CVE-2022-3344"},"packages":[],"prev":{"headline":"Jetpack CRM \u003c= 5.3.1 - Cross-Site Request Forgery and PHAR Deserialization","id":"CVE-2022-3342"},"products":["Discy","Himer","WPQA Builder"],"published":"2023-01-09","related":[{"cvss_score":8.8,"headline":"WPQA \u003c 6.1.1 - Arbitrary Category and Tag Follow/Unfollow via CSRF","id":"CVE-2024-2376","kev_date_added":null,"published":"2024-07-03"},{"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-09","vendors":["Unknown"]},"summary":"Attackers can inflate user scores by exploiting missing validation in the WPQA Builder plugin's follow functionality.","url":"https://insights.sbomify.com/CVE-2022-3343/"}