{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24379 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24379 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24379 is a medium-severity vulnerability in Unknown Comments Like Dislike, published on 21 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-24379 and fix it if it is affected.\n\nWhat it is: CVE-2021-24379 is a medium-severity vulnerability in Unknown Comments Like Dislike, published on 21 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-24379 in the wild and no public exploit code.\n\nAffected product: Unknown Comments Like Dislike. 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-24379/ (Markdown: https://insights.sbomify.com/CVE-2021-24379/index.md)","id":"CVE-2021-24379","markdown":"https://insights.sbomify.com/CVE-2021-24379/index.md","name":"CVE-2021-24379","record":{"aliases":["GHSA-vww6-xqpq-4v62"],"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 bypass client-side restrictions to add unlimited likes or dislikes to any comment, compromising data integrity.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"comments_like_dislike","vendor":"wphappycoders"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The Comments Like Dislike WordPress plugin before 1.1.4 allows users to like/dislike posted comments, however does not prevent them from replaying the AJAX request to add a like. This allows any user (even unauthenticated) to add unlimited like/dislike to any comment. The plugin appears to have some Restriction modes, such as Cookie Restriction, IP Restrictions, Logged In User Restriction, however, they do not prevent such attack as they only check client side","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":"Comments Like Dislike \u003c 1.1.4 - Add Like/Dislike Bypass","id":"CVE-2021-24379","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Shantz WordPress QOTD \u003c= 1.2.2 - Arbitrary Setting Update via CSRF","id":"CVE-2021-24380"},"packages":[],"prev":{"headline":"Autoptimize \u003c 2.7.8 - Authenticated Stored XSS via File Upload","id":"CVE-2021-24378"},"products":["Comments Like Dislike"],"published":"2021-06-21","related":[{"cvss_score":4.3,"headline":"Comments Like Dislike \u003c= 1.2.0 - Missing Authorization to Authenticated (Subscriber+) Plugin Setting Reset","id":"CVE-2023-3244","kev_date_added":null,"published":"2023-08-17"}],"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":["Unknown"]},"summary":"Attackers can bypass client-side restrictions to add unlimited likes or dislikes to any comment, compromising data integrity.","url":"https://insights.sbomify.com/CVE-2021-24379/"}