{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-54303 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-54303 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54303 is a critical vulnerability in n/a, published on 4 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-54303 and fix it if it is affected.\n\nWhat it is: CVE-2025-54303 is a critical vulnerability in n/a, published on 4 Dec 2025. 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-2025-54303 in the wild and no public exploit code.\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-54303/ (Markdown: https://insights.sbomify.com/CVE-2025-54303/index.md)","id":"CVE-2025-54303","markdown":"https://insights.sbomify.com/CVE-2025-54303/index.md","name":"CVE-2025-54303","record":{"aliases":["GHSA-p4v2-9grq-vm24"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Torrent Suite Django app","requires_auth":"none","summary":"Attackers can authenticate as admin using default credentials in Torrent Suite, leading to full system compromise if passwords are not changed.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"torrent_suite_software","vendor":"thermofisher"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1392","name":"Use of Default Credentials"}],"description":"The Thermo Fisher Torrent Suite Django application 5.18.1 has weak default credentials, which are stored as fixtures for the Django ORM API. The ionadmin user account can be used to authenticate to default deployments with the password ionadmin. The user guide recommends changing default credentials; however, a password change policy for default administrative accounts is not enforced. Many deployments may retain default credentials, in which case an attacker is likely to be able to successfully authenticate with administrative privileges.","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":"Hardcoded credentials in n/a","id":"CVE-2025-54303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2025-54304"},"packages":[],"prev":{"headline":"Extension - norrnext.com - Stored XSS vulnerability in Quantum Manager component 1.0.0-3.2.0 for Joomla","id":"CVE-2025-54301"},"products":["n/a"],"published":"2025-12-04","related":[{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2025-54307","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":7.8,"headline":"Auth bypass in n/a","id":"CVE-2025-54305","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":7.2,"headline":"Command injection in n/a","id":"CVE-2025-54306","kev_date_added":null,"published":"2025-12-04"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-05","vendors":["n/a"]},"summary":"Attackers can authenticate as admin using default credentials in Torrent Suite, leading to full system compromise if passwords are not changed.","url":"https://insights.sbomify.com/CVE-2025-54303/"}