{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6669 exists.","fix":"No fix has been published for CVE-2025-6669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6669 is a medium-severity vulnerability in gooaclok819 sublinkX, published on 25 Jun 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-6669 and fix it if it is affected.\n\nWhat it is: CVE-2025-6669 is a medium-severity vulnerability in gooaclok819 sublinkX, published on 25 Jun 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-6669 exists.\n\nAffected product: gooaclok819 sublinkX. 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-6669/ (Markdown: https://insights.sbomify.com/CVE-2025-6669/index.md)","id":"CVE-2025-6669","markdown":"https://insights.sbomify.com/CVE-2025-6669/index.md","name":"CVE-2025-6669","record":{"aliases":["GHSA-gfjv-xv9m-gwx5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"sublinkX URL shortener","requires_auth":"none","summary":"An attacker can bypass JWT authentication in sublinkX by exploiting a hard-coded cryptographic key, potentially gaining unauthorized access.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"description":"A vulnerability was found in gooaclok819 sublinkX up to 1.8. It has been declared as problematic. This vulnerability affects unknown code of the file middlewares/jwt.go. The manipulation with the input sublink leads to use of hard-coded cryptographic key\r . The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 1.9 is able to address this issue. The patch is identified as 778d26aef723daa58df98c8060c43f5bf5d1b10b. It is recommended to upgrade the affected component.","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":"gooaclok819 sublinkX jwt.go hard-coded key","id":"CVE-2025-6669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"Cross-Site Request Forgery (CSRF) in Multiple WSO2 Products via HTTP GET in Admin Services","id":"CVE-2025-6670"},"packages":[],"prev":{"headline":"code-projects Inventory Management System fetchSelectedBrand.php sql injection","id":"CVE-2025-6668"},"products":["sublinkX"],"published":"2025-06-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-07-01","vendors":["gooaclok819"]},"summary":"An attacker can bypass JWT authentication in sublinkX by exploiting a hard-coded cryptographic key, potentially gaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2025-6669/"}