{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67418 exists.","fix":"No fix has been published for CVE-2025-67418 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67418 is a critical vulnerability in n/a, published on 22 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-67418 and fix it if it is affected.\n\nWhat it is: CVE-2025-67418 is a critical vulnerability in n/a, published on 22 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-67418 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-67418/ (Markdown: https://insights.sbomify.com/CVE-2025-67418/index.md)","id":"CVE-2025-67418","markdown":"https://insights.sbomify.com/CVE-2025-67418/index.md","name":"CVE-2025-67418","record":{"aliases":["GHSA-99ch-5w4g-r777"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"ClipBucket video platform","requires_auth":"none","summary":"Unauthenticated attackers can gain full administrative control of ClipBucket by logging in with hardcoded default credentials.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"clipbucket","vendor":"oxygenz"}],"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-798","name":"Use of Hard-coded Credentials"}],"description":"ClipBucket 5.5.2 is affected by an improper access control issue where the product is shipped or deployed with hardcoded default administrative credentials. An unauthenticated remote attacker can log in to the administrative panel using these default credentials, resulting in full administrative control of the application.","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":"Hardcoded credentials in n/a","id":"CVE-2025-67418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"evershop allows unauthenticated attackers to exhaust application server's resources via \"GET /images\" API","id":"CVE-2025-67419"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-67408"},"products":["n/a"],"published":"2025-12-22","related":[{"cvss_score":9.8,"headline":"ClipBucket v5 Vulnerable to Blind SQL Injection through Channel Comments","id":"CVE-2026-21875","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":9.8,"headline":"ClipBucket V5 Playlist Cover File Upload to Remote Code Execution","id":"CVE-2025-21624","kev_date_added":null,"published":"2025-01-07"},{"cvss_score":9.8,"headline":"Untrusted Deserialization in ClipBucket-v5 Version 2.0 to 5.5.1 Revision 199","id":"CVE-2024-54135","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Untrusted Deserialization in ClipBucket-v5 Version 5.5.1 Revision 199 and Below","id":"CVE-2024-54136","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.3,"headline":"ClipBucket v5 Affected by Remote Code Execution via Avatar/Background File Upload Race Condition","id":"CVE-2026-25728","kev_date_added":null,"published":"2026-02-10"},{"cvss_score":8.8,"headline":"ClipBucket v5 has time-based Blind SQL Injection in ajax.php that leads to Data Exfiltration","id":"CVE-2026-32321","kev_date_added":null,"published":"2026-03-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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can gain full administrative control of ClipBucket by logging in with hardcoded default credentials.","url":"https://insights.sbomify.com/CVE-2025-67418/"}