{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0424 exists.","fix":"No fix has been published for CVE-2022-0424 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-0424 is a medium-severity missing authorization vulnerability in Unknown Popup by Supsystic, published on 9 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-0424 and fix it if it is affected.\n\nWhat it is: CVE-2022-0424 is a medium-severity missing authorization vulnerability in Unknown Popup by Supsystic, published on 9 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0424 exists.\n\nAffected product: Unknown 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-2022-0424/ (Markdown: https://insights.sbomify.com/CVE-2022-0424/index.md)","id":"CVE-2022-0424","markdown":"https://insights.sbomify.com/CVE-2022-0424/index.md","name":"CVE-2022-0424","record":{"aliases":["GHSA-28vh-fggg-795m"],"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 access subscriber email addresses via an unprotected AJAX action in the Popup by Supsystic plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"popup","vendor":"supsystic"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","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-306","name":"Missing Authentication for Critical Functionality"}],"description":"The Popup by Supsystic WordPress plugin before 1.10.9 does not have any authentication and authorisation in an AJAX action, allowing unauthenticated attackers to call it and get the email addresses of subscribed users","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/2022/CVE-2022-0424.yaml","stars":null,"title":"Popup by Supsystic \u003c 1.10.9 - Subscriber Email Addresses Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Popup by Supsystic \u003c 1.10.9 - Unauthenticated Subscriber Email Addresses Disclosure","id":"CVE-2022-0424","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in GitLab","id":"CVE-2022-0425"},"packages":[],"prev":{"headline":"3D FlipBook \u003c 1.12.1 - Subscriber+ Stored Cross-Site Scripting","id":"CVE-2022-0423"},"products":["Popup by Supsystic"],"published":"2022-05-09","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"},{"cvss_score":5.3,"headline":"WordPress Popup by Supsystic plugin \u003c= 1.10.19 - Unauthenticated Subscriber Email Addresses Disclosure","id":"CVE-2023-46197","kev_date_added":null,"published":"2024-05-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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Unauthenticated attackers can access subscriber email addresses via an unprotected AJAX action in the Popup by Supsystic plugin.","url":"https://insights.sbomify.com/CVE-2022-0424/"}