{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10196 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10196 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10196 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Mar 2020. 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-2020-10196 and fix it if it is affected.\n\nWhat it is: CVE-2020-10196 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Mar 2020. 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-2020-10196 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-10196/ (Markdown: https://insights.sbomify.com/CVE-2020-10196/index.md)","id":"CVE-2020-10196","markdown":"https://insights.sbomify.com/CVE-2020-10196/index.md","name":"CVE-2020-10196","record":{"aliases":["GHSA-3mqf-h9j7-cgh5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress popup-builder plugin","requires_auth":"none","summary":"Remote attackers can inject arbitrary JavaScript into WordPress popups via an unsecured AJAX action, executing code in visitors' browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"popup_builder","vendor":"sygnoos"}],"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-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"An XSS vulnerability in the popup-builder plugin before 3.64.1 for WordPress allows remote attackers to inject arbitrary JavaScript into existing popups via an unsecured ajax action in com/classes/Ajax.php. It is possible for an unauthenticated attacker to insert malicious JavaScript in several of the popup's fields by sending a request to wp-admin/admin-ajax.php with the POST action parameter of sgpb_autosave and including additional data in an allPopupData parameter, including the popup's ID (which is visible in the source of the page in which the popup is inserted) and arbitrary JavaScript which will then be executed in the browsers of visitors to that page. Because the plugin functionality automatically adds script tags to data entered into these fields, this injection will typically bypass most WAF applications.","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":"Cross-site scripting in n/a","id":"CVE-2020-10196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Sonatype Nexus Repository Remote Code Execution","id":"CVE-2020-10199"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-10195"},"products":["n/a"],"published":"2020-03-13","related":[{"cvss_score":9.8,"headline":"Popup Builder \u003c 4.1.1 - SQL Injection to Reflected Cross-Site Scripting","id":"CVE-2022-0479","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-9006","kev_date_added":null,"published":"2020-02-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-14695","kev_date_added":null,"published":"2019-08-06"},{"cvss_score":8.8,"headline":"Popup Builder \u003c 4.0.7 - LFI to RCE","id":"CVE-2021-25082","kev_date_added":null,"published":"2022-02-21"},{"cvss_score":8.1,"headline":"Missing authorization in Popup Builder – Create highly converting, mobile friendly marketing popups.","id":"CVE-2023-6696","kev_date_added":null,"published":"2024-06-15"},{"cvss_score":7.5,"headline":"popup-builder \u003c 4.2.6 - Admin+ SSRF \u0026 File Read","id":"CVE-2023-6294","kev_date_added":null,"published":"2024-02-12"},{"cvss_score":7.4,"headline":"Popup Builder \u003c= 4.3.0 - Missing Authorization in Multiple AJAX Actions","id":"CVE-2024-2544","kev_date_added":null,"published":"2024-06-15"}],"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":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary JavaScript into WordPress popups via an unsecured AJAX action, executing code in visitors' browsers.","url":"https://insights.sbomify.com/CVE-2020-10196/"}