{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6851 exists.","fix":"No fix has been published for CVE-2025-6851 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6851 is a high-severity server-side request forgery vulnerability in apos37 Broken Link Notifier, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6851 and fix it if it is affected.\n\nWhat it is: CVE-2025-6851 is a high-severity server-side request forgery vulnerability in apos37 Broken Link Notifier, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6851 exists.\n\nAffected product: apos37 Broken Link Notifier. 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-2025-6851/ (Markdown: https://insights.sbomify.com/CVE-2025-6851/index.md)","id":"CVE-2025-6851","markdown":"https://insights.sbomify.com/CVE-2025-6851/index.md","name":"CVE-2025-6851","record":{"aliases":["GHSA-x4vc-m5g5-663m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit Broken Link Notifier to perform Server-Side Request Forgery, accessing internal services.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"broken_link_notifier","vendor":"pluginrx"}],"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-918","name":"Server-Side Request Forgery"}],"description":"The Broken Link Notifier plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.3.0 via the ajax_blinks() function which ultimately calls the check_url_status_code() function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-6851.yaml","stars":null,"title":"WordPress Broken Link Notifier \u003c 1.3.1 - Unauthenticated SSRF"}],"tier":"weaponised"},"has_fix":null,"headline":"Broken Link Notifier \u003c= 1.3.0 - Unauthenticated Server-Side Request Forgery","id":"CVE-2025-6851","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"chatchat-space Langchain-Chatchat Backend upload_temp_docs path traversal","id":"CVE-2025-6853"},"packages":[],"prev":{"headline":"code-projects Simple Forum forum1.php sql injection","id":"CVE-2025-6850"},"products":["Broken Link Notifier"],"published":"2025-07-11","related":[],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["apos37"]},"summary":"Unauthenticated attackers can exploit Broken Link Notifier to perform Server-Side Request Forgery, accessing internal services.","url":"https://insights.sbomify.com/CVE-2025-6851/"}