{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8549 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8549 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8549 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Feb 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-8549 and fix it if it is affected.\n\nWhat it is: CVE-2020-8549 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Feb 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-8549 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-8549/ (Markdown: https://insights.sbomify.com/CVE-2020-8549/index.md)","id":"CVE-2020-8549","markdown":"https://insights.sbomify.com/CVE-2020-8549/index.md","name":"CVE-2020-8549","record":{"aliases":["GHSA-4x75-37xv-wgwv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Stored XSS in Strong Testimonials allows attackers to steal session tokens, potentially leading to account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"strong_testimonials","vendor":"wpchill"}],"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":"Stored XSS in the Strong Testimonials plugin before 2.40.1 for WordPress can result in an attacker performing malicious actions such as stealing session tokens.","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-8549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":5,"next":{"headline":"Kubernetes kubelet denial of service","id":"CVE-2020-8551"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-8548"},"products":["n/a"],"published":"2020-02-03","related":[{"cvss_score":6.5,"headline":"WordPress Strong Testimonials Plugin \u003c= 3.0.2 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-26013","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":4.8,"headline":"Strong Testimonials \u003c 3.1.12 - Contributor+ Stored XSS","id":"CVE-2024-3261","kev_date_added":null,"published":"2024-04-24"},{"cvss_score":4.3,"headline":"WordPress Strong Testimonials plugin \u003c= 3.1.16 - Broken Access Control vulnerability","id":"CVE-2024-47362","kev_date_added":null,"published":"2024-11-01"},{"cvss_score":4.3,"headline":"Strong Testimonials \u003c= 3.1.12 - Authenticated(Contributor+) Improper Authorization to Views Modification","id":"CVE-2023-6491","kev_date_added":null,"published":"2024-06-07"},{"cvss_score":4.3,"headline":"WordPress Strong Testimonials Plugin \u003c= 3.1.10 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-52123","kev_date_added":null,"published":"2024-01-05"}],"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":"Stored XSS in Strong Testimonials allows attackers to steal session tokens, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2020-8549/"}