{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24838 exists.","fix":"No fix has been published for CVE-2021-24838 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24838 is a medium-severity vulnerability in Unknown AnyComment, published on 17 Jan 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-2021-24838 and fix it if it is affected.\n\nWhat it is: CVE-2021-24838 is a medium-severity vulnerability in Unknown AnyComment, published on 17 Jan 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24838 exists.\n\nAffected product: Unknown AnyComment. 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-24838/ (Markdown: https://insights.sbomify.com/CVE-2021-24838/index.md)","id":"CVE-2021-24838","markdown":"https://insights.sbomify.com/CVE-2021-24838/index.md","name":"CVE-2021-24838","record":{"aliases":["GHSA-3cq7-3xmj-m7r2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can redirect users to malicious sites via an unvalidated redirect parameter in the AnyComment WordPress plugin.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"anycomment","vendor":"bologer"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"The AnyComment WordPress plugin before 0.3.5 has an API endpoint which passes user input via the redirect parameter to the wp_redirect() function without being validated first, leading to an Open Redirect issue, which according to the vendor, is a feature.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2021/CVE-2021-24838.yaml","stars":null,"title":"WordPress AnyComment \u003c0.3.5 - Open Redirect"}],"tier":"weaponised"},"has_fix":null,"headline":"AnyComment \u003c 0.3.5 - Open Redirect","id":"CVE-2021-24838","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"SupportCandy \u003c 2.2.5 - Unauthenticated Arbitrary Ticket Deletion","id":"CVE-2021-24839"},"packages":[],"prev":{"headline":"Passster \u003c 3.5.5.8 - Contributor+ Stored Cross-Site Scripting","id":"CVE-2021-24837"},"products":["AnyComment"],"published":"2022-01-17","related":[{"cvss_score":8.8,"headline":"AnyComment \u003c 0.2.18 - Arbitrary HyperComments Import/Revert via CSRF","id":"CVE-2022-0134","kev_date_added":null,"published":"2022-02-21"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-21001","kev_date_added":null,"published":"2019-08-27"},{"cvss_score":3.1,"headline":"AnyComment \u003c 0.2.18 - Comment Rating Increase/Decrease via Race Condition","id":"CVE-2022-0279","kev_date_added":null,"published":"2022-02-21"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"An attacker can redirect users to malicious sites via an unvalidated redirect parameter in the AnyComment WordPress plugin.","url":"https://insights.sbomify.com/CVE-2021-24838/"}