{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2405 exists.","fix":"No fix has been published for CVE-2022-2405 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2405 is a medium-severity missing authorization vulnerability in Unknown WP Popup Builder – Popup Forms , Marketing PoPuP \u0026  Newsletter, published on 26 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-2405 and fix it if it is affected.\n\nWhat it is: CVE-2022-2405 is a medium-severity missing authorization vulnerability in Unknown WP Popup Builder – Popup Forms , Marketing PoPuP \u0026  Newsletter, published on 26 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2405 exists.\n\nAffected product: Unknown WP Popup Builder – Popup Forms , Marketing PoPuP \u0026  Newsletter. 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-2405/ (Markdown: https://insights.sbomify.com/CVE-2022-2405/index.md)","id":"CVE-2022-2405","markdown":"https://insights.sbomify.com/CVE-2022-2405/index.md","name":"CVE-2022-2405","record":{"aliases":["GHSA-wmh8-mcwp-x84h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated users can delete arbitrary popups due to missing authorization and CSRF checks in an AJAX action.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_popup_builder","vendor":"themehunk"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Popup Builder WordPress plugin before 1.2.9 does not have authorisation and CSRF check in an AJAX action, allowing any authenticated users, such as subscribers to delete arbitrary Popup","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WP Popup Builder \u003c 1.3.0 - Subscriber+ Arbitrary Popup Deletion","id":"CVE-2022-2405","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":"Malicious imports can lead to Denial of Service","id":"CVE-2022-2406"},"packages":[],"prev":{"headline":"WP Popup Builder \u003c 1.2.9 - Reflected Cross-Site Scripting","id":"CVE-2022-2404"},"products":["WP Popup Builder – Popup Forms , Marketing PoPuP \u0026  Newsletter"],"published":"2022-09-26","related":[{"cvss_score":7.3,"headline":"Code injection in WP Popup Builder – Popup Forms and Marketing Lead Generation","id":"CVE-2024-9061","kev_date_added":null,"published":"2024-10-16"},{"cvss_score":6.1,"headline":"WP Popup Builder \u003c 1.2.9 - Reflected Cross-Site Scripting","id":"CVE-2022-2404","kev_date_added":null,"published":"2022-09-26"},{"cvss_score":5.3,"headline":"WordPress WP Popup Builder plugin \u003c= 1.3.8 - Sensitive Data Exposure vulnerability","id":"CVE-2025-62902","kev_date_added":null,"published":"2025-10-27"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-21","vendors":["Unknown"]},"summary":"Authenticated users can delete arbitrary popups due to missing authorization and CSRF checks in an AJAX action.","url":"https://insights.sbomify.com/CVE-2022-2405/"}