{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-75528 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75528 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75528 is a high-severity cross-site scripting vulnerability in wpmudev Broken Link Checker, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-75528 and fix it if it is affected.\n\nWhat it is: CVE-2026-75528 is a high-severity cross-site scripting vulnerability in wpmudev Broken Link Checker, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-75528 in the wild and no public exploit code.\n\nAffected product: wpmudev Broken Link Checker. 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-2026-75528/ (Markdown: https://insights.sbomify.com/CVE-2026-75528/index.md)","id":"CVE-2026-75528","markdown":"https://insights.sbomify.com/CVE-2026-75528/index.md","name":"CVE-2026-75528","record":{"aliases":["GHSA-qpv7-fm86-f6w8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via comment author URLs, executing code when administrators review link logs.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author URL / Link Log in all versions up to, and including, 2.4.13 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires an administrator to perform the plugin's standard dismiss-and-recheck workflow on a link submitted by the attacker via the WordPress comment author URL field, after which the attacker's HTTP server issues a redirect to a URL containing an HTML/JavaScript payload that is stored verbatim in the link log.","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":"Broken Link Checker \u003c= 2.4.13 - Unauthenticated Stored Cross-Site Scripting via Comment Author URL / Link Log","id":"CVE-2026-75528","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":13,"next":{"headline":"Stored Cross-Site Scripting via MIME-Type Confusion in PDF Downloads of Pandora","id":"CVE-2026-75529"},"packages":[],"prev":{"headline":"django CMS: Stored XSS in edit-mode plugin exception rendering","id":"CVE-2026-75526"},"products":["Broken Link Checker"],"published":"2026-09-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["wpmudev"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via comment author URLs, executing code when administrators review link logs.","url":"https://insights.sbomify.com/CVE-2026-75528/"}