{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46197 is a medium-severity path traversal vulnerability in supsystic.com Popup by Supsystic, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-46197 and fix it if it is affected.\n\nWhat it is: CVE-2023-46197 is a medium-severity path traversal vulnerability in supsystic.com Popup by Supsystic, published on 17 May 2024. 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-2023-46197 in the wild and no public exploit code.\n\nAffected product: supsystic.com Popup by Supsystic. 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-46197/ (Markdown: https://insights.sbomify.com/CVE-2023-46197/index.md)","id":"CVE-2023-46197","markdown":"https://insights.sbomify.com/CVE-2023-46197/index.md","name":"CVE-2023-46197","record":{"aliases":["GHSA-5w4j-qp2j-2p4h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit a path traversal flaw to disclose subscriber email addresses in the Popup by Supsystic WordPress plugin.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"popup","vendor":"supsystic"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in supsystic.Com Popup by Supsystic allows Relative Path Traversal.This issue affects Popup by Supsystic: from n/a through 1.10.19.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-10-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-10-23T12:38:37Z","kind":"github_poc","ref":"https://github.com/RandomRobbieBF/CVE-2023-46197","stars":0,"title":"Popup by Supsystic \u003c= 1.10.19 - Missing Authorization to Sensitive Information Exposure"}],"tier":"poc_unverified"},"has_fix":null,"headline":"WordPress Popup by Supsystic plugin \u003c= 1.10.19 - Unauthenticated Subscriber Email Addresses Disclosure","id":"CVE-2023-46197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Appointment Calendar Plugin \u003c= 2.9.6 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-46198"},"packages":[],"prev":{"headline":"WordPress Social proof testimonials and reviews by Repuso plugin \u003c= 4.97 - Broken Access Control vulnerability","id":"CVE-2023-46196"},"products":["Popup by Supsystic"],"published":"2024-05-17","related":[{"cvss_score":9.8,"headline":"Supsystic Popup \u003c 1.10.19 - Prototype Pollution","id":"CVE-2023-3186","kev_date_added":null,"published":"2023-07-17"},{"cvss_score":9.1,"headline":"WordPress Popup by Supsystic plugin \u003c= 1.10.29 - Remote Code Execution (RCE) vulnerability","id":"CVE-2024-52434","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2016-10915","kev_date_added":null,"published":"2019-08-20"},{"cvss_score":6.1,"headline":"Popup by Supsystic \u003c 1.10.5 - Reflected Cross-Site scripting (XSS)","id":"CVE-2021-24275","kev_date_added":null,"published":"2021-05-05"},{"cvss_score":5.3,"headline":"WordPress Popup by Supsystic plugin \u003c= 1.10.19 - Broken Access Control Vulnerability","id":"CVE-2023-39997","kev_date_added":null,"published":"2024-12-13"},{"cvss_score":5.3,"headline":"WordPress Popup by Supsystic plugin \u003c= 1.10.19 - Broken Access Control vulnerability","id":"CVE-2023-51353","kev_date_added":null,"published":"2024-12-09"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["supsystic.com"]},"summary":"Unauthenticated attackers can exploit a path traversal flaw to disclose subscriber email addresses in the Popup by Supsystic WordPress plugin.","url":"https://insights.sbomify.com/CVE-2023-46197/"}