{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-49197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49197 is a medium-severity vulnerability in Apasionados, Apasionados del Marketing, NetConsulting DoFollow Case by Case, published on 15 Dec 2023. 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-2023-49197 and fix it if it is affected.\n\nWhat it is: CVE-2023-49197 is a medium-severity vulnerability in Apasionados, Apasionados del Marketing, NetConsulting DoFollow Case by Case, published on 15 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-49197 in the wild and no public exploit code.\n\nAffected product: Apasionados, Apasionados del Marketing, NetConsulting DoFollow Case by Case. 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-2023-49197/ (Markdown: https://insights.sbomify.com/CVE-2023-49197/index.md)","id":"CVE-2023-49197","markdown":"https://insights.sbomify.com/CVE-2023-49197/index.md","name":"CVE-2023-49197","record":{"aliases":["GHSA-q8x8-6c79-7jxf"],"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":"Attackers can trick authenticated users into performing unwanted actions in the DoFollow Case by Case WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"dofollow_case_by_case","vendor":"apasionados"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in Apasionados, Apasionados del Marketing, NetConsulting DoFollow Case by Case.This issue affects DoFollow Case by Case: from n/a through 3.4.2.","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":"WordPress DoFollow Case by Case Plugin \u003c= 3.4.2 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-49197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Apache SeaTunnel Web: Arbitrary file read vulnerability","id":"CVE-2023-49198"},"packages":[],"prev":{"headline":"WordPress Pagelayer plugin \u003c= 1.7.7 - Broken Access Control vulnerability","id":"CVE-2023-49196"},"products":["DoFollow Case by Case"],"published":"2023-12-15","related":[{"cvss_score":5.9,"headline":"WordPress DoFollow Case by Case plugin \u003c= 3.5.1 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-47625","kev_date_added":null,"published":"2025-05-07"},{"cvss_score":4.3,"headline":"WordPress DoFollow Case by Case plugin \u003c= 3.5.1 - Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2025-47624","kev_date_added":null,"published":"2025-05-07"}],"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":"2026-04-28","vendors":["Apasionados, Apasionados del Marketing, NetConsulting"]},"summary":"Attackers can trick authenticated users into performing unwanted actions in the DoFollow Case by Case WordPress plugin.","url":"https://insights.sbomify.com/CVE-2023-49197/"}