{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16521 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16521 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16521 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Oct 2019. 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-2019-16521 and fix it if it is affected.\n\nWhat it is: CVE-2019-16521 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Oct 2019. 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-2019-16521 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-2019-16521/ (Markdown: https://insights.sbomify.com/CVE-2019-16521/index.md)","id":"CVE-2019-16521","markdown":"https://insights.sbomify.com/CVE-2019-16521/index.md","name":"CVE-2019-16521","record":{"aliases":["GHSA-48cc-3r5m-2jp3"],"analysis":{"component_type":"cms_plugin","fix_type":"end_of_life","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Reflected XSS in Broken Link Checker allows attackers to execute scripts via crafted GET parameters, affecting end-of-life WordPress installations.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"broken_link_checker","vendor":"managewp"}],"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":"The broken-link-checker plugin through 1.11.8 for WordPress (aka Broken Link Checker) is susceptible to Reflected XSS due to improper encoding and insertion of an HTTP GET parameter into HTML. The filter function on the page listing all detected broken links can be exploited by providing an XSS payload in the s_filter GET parameter in a filter_id=search request. NOTE: this is an end-of-life product.","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-2019-16521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16522"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16520"},"products":["n/a"],"published":"2019-10-16","related":[{"cvss_score":9.3,"headline":"WordPress MainWP Broken Links Checker Extension Plugin \u003c= 4.0 is vulnerable to SQL Injection","id":"CVE-2023-23737","kev_date_added":null,"published":"2023-10-12"},{"cvss_score":7.2,"headline":"Broken Link Checker \u003c= 1.11.16 - Authenticated (Admin+) PHAR Deserialization","id":"CVE-2022-2438","kev_date_added":null,"published":"2022-09-06"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2019-17207","kev_date_added":null,"published":"2019-10-18"},{"cvss_score":4.8,"headline":"Broken Link Checker \u003c 1.11.20 - Admin+ Cross-Site Scripting","id":"CVE-2022-3922","kev_date_added":null,"published":"2022-12-28"},{"cvss_score":4.7,"headline":"Broken Link Checker \u003c 2.4.2 - Admin+ SSRF","id":"CVE-2024-10903","kev_date_added":null,"published":"2024-12-26"},{"cvss_score":2.4,"headline":"Broken Link Checker Plugin Settings Page core.php options_page cross site scripting","id":"CVE-2014-125105","kev_date_added":null,"published":"2023-06-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-05","vendors":["n/a"]},"summary":"Reflected XSS in Broken Link Checker allows attackers to execute scripts via crafted GET parameters, affecting end-of-life WordPress installations.","url":"https://insights.sbomify.com/CVE-2019-16521/"}