{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62719 exists.","fix":"No fix has been published for CVE-2025-62719 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62719 is a low-severity server-side request forgery vulnerability in Kovah LinkAce, published on 4 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62719 and fix it if it is affected.\n\nWhat it is: CVE-2025-62719 is a low-severity server-side request forgery vulnerability in Kovah LinkAce, published on 4 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62719 exists.\n\nAffected product: Kovah LinkAce. 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-62719/ (Markdown: https://insights.sbomify.com/CVE-2025-62719/index.md)","id":"CVE-2025-62719","markdown":"https://insights.sbomify.com/CVE-2025-62719/index.md","name":"CVE-2025-62719","record":{"aliases":["GHSA-473x-rmm6-mc8c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"LinkAce link archive","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit SSRF in LinkAce to scan internal networks and discover services, though data exfiltration is limited.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"linkace","vendor":"linkace"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"LinkAce is a self-hosted archive to collect website links. In versions 2.3.0 and below, the htmlKeywordsFromUrl function in the FetchController class accepts user-provided URLs and makes HTTP requests to them without validating that the destination is not an internal or private network resource. This Server-Side Request Forgery (SSRF) vulnerability allows authenticated attackers to use the application server to perform port scanning and service discovery on internal networks. Practical impact is very limited because the function only extracts content from HTML meta keywords tags, which prevents meaningful data exfiltration from databases, APIs, or cloud metadata endpoints. This issue is fixed in version 2.4.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LinkAce: Limited Server-Side Request Forgery (SSRF) in Keyword Fetching Functionality","id":"CVE-2025-62719","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"LinkAce: Data Exfiltration via Export Functions Allow Access to All Users' Private Links","id":"CVE-2025-62720"},"packages":[],"prev":{"headline":"Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF","id":"CVE-2025-62718"},"products":["LinkAce"],"published":"2025-11-04","related":[{"cvss_score":8.7,"headline":"LinkAce: Stored XSS in Atom Feed via CDATA Escape in List Description","id":"CVE-2026-27458","kev_date_added":null,"published":"2026-02-21"},{"cvss_score":8.7,"headline":"LinkAce: Stored XSS Vulnerability in Link Title Field Through Social Media Sharing Feature","id":"CVE-2025-62722","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":8.5,"headline":"LinkAce's SSRF protection can be bypassed via internal hostname resolution in LinkAce","id":"CVE-2026-33953","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":8.4,"headline":"LinkAce has a Stored One Click XSS vulnerability","id":"CVE-2025-53838","kev_date_added":null,"published":"2025-09-08"},{"cvss_score":7.7,"headline":"LinkAce affected by SSRF via link creation: NoPrivateIpRule not applied to LinkStoreRequest","id":"CVE-2026-30953","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.6,"headline":"File Upload Vulnerability Leading to XSS in LinkAce v1.15.5","id":"CVE-2024-56508","kev_date_added":null,"published":"2024-12-27"},{"cvss_score":7.3,"headline":"LinkAce Vulnerable to Stored XSS on the Audit Page","id":"CVE-2025-59424","kev_date_added":null,"published":"2025-09-18"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-05","vendors":["Kovah"]},"summary":"Authenticated attackers can exploit SSRF in LinkAce to scan internal networks and discover services, though data exfiltration is limited.","url":"https://insights.sbomify.com/CVE-2025-62719/"}