{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65427 exists.","fix":"No fix has been published for CVE-2025-65427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65427 is a medium-severity vulnerability in n/a, published on 16 Dec 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-65427 and fix it if it is affected.\n\nWhat it is: CVE-2025-65427 is a medium-severity vulnerability in n/a, published on 16 Dec 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-65427 exists.\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-2025-65427/ (Markdown: https://insights.sbomify.com/CVE-2025-65427/index.md)","id":"CVE-2025-65427","markdown":"https://insights.sbomify.com/CVE-2025-65427/index.md","name":"CVE-2025-65427","record":{"aliases":["GHSA-6vj9-7994-7367"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Wireless Wi-Fi Router","requires_auth":"none","summary":"Attackers can brute force passwords on the Dbit N300 T1 Pro router due to missing rate limiting on the login API.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dbit_n300_t1_pro_firmware","vendor":"dbitnet"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"An issue was discovered in Dbit N300 T1 Pro Easy Setup Wireless Wi-Fi Router on firmware version V1.0.0 does not implement rate limiting to /api/login allowing attackers to brute force password enumerations.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-12-16","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-12-16T04:29:58Z","kind":"github_poc","ref":"https://github.com/kirubel-cve/CVE-2025-65427","stars":0,"title":"CVE-2025-65427: Missing rate limiting in Dbit N300 T1 Pro router login API allows brute-force attacks"}],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2025-65427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"django-allauth does not reject access tokens for inactive users","id":"CVE-2025-65430"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-65418"},"products":["n/a"],"published":"2025-12-16","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2026-36956","kev_date_added":null,"published":"2026-04-30"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2026-36957","kev_date_added":null,"published":"2026-04-30"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can brute force passwords on the Dbit N300 T1 Pro router due to missing rate limiting on the login API.","url":"https://insights.sbomify.com/CVE-2025-65427/"}