{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10410 exists.","fix":"No fix has been published for CVE-2025-10410 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10410 is a medium-severity server-side request forgery vulnerability in SourceCodester Link Status Checker, published on 14 Sep 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-10410 and fix it if it is affected.\n\nWhat it is: CVE-2025-10410 is a medium-severity server-side request forgery vulnerability in SourceCodester Link Status Checker, published on 14 Sep 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-10410 exists.\n\nAffected product: SourceCodester Link Status 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-2025-10410/ (Markdown: https://insights.sbomify.com/CVE-2025-10410/index.md)","id":"CVE-2025-10410","markdown":"https://insights.sbomify.com/CVE-2025-10410/index.md","name":"CVE-2025-10410","record":{"aliases":["GHSA-8f96-5hjm-cvqf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Link Status Checker","requires_auth":"low_privilege","summary":"Remote attackers can exploit a server-side request forgery vulnerability in the Link Status Checker application via the proxy argument.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"link_status_checker","vendor":"rems"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A security vulnerability has been detected in SourceCodester Link Status Checker 1.0. This vulnerability affects unknown code of the file index.php. The manipulation of the argument proxy leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"SourceCodester Link Status Checker index.php server-side request forgery","id":"CVE-2025-10410","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"itsourcecode E-Logbook with Health Monitoring System for COVID-19 POST Request check_profile.php cross site scripting","id":"CVE-2025-10411"},"packages":[],"prev":{"headline":"SourceCodester Student Grading System rms.php sql injection","id":"CVE-2025-10409"},"products":["Link Status Checker"],"published":"2025-09-14","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-60313","kev_date_added":null,"published":"2025-10-08"}],"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-09-15","vendors":["SourceCodester"]},"summary":"Remote attackers can exploit a server-side request forgery vulnerability in the Link Status Checker application via the proxy argument.","url":"https://insights.sbomify.com/CVE-2025-10410/"}