{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-23027 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-23027 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-23027 is a medium-severity vulnerability in haydenbleasel next-forge, published on 13 Jan 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-23027 and fix it if it is affected.\n\nWhat it is: CVE-2025-23027 is a medium-severity vulnerability in haydenbleasel next-forge, published on 13 Jan 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-23027 in the wild and no public exploit code.\n\nAffected product: haydenbleasel next-forge. 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-23027/ (Markdown: https://insights.sbomify.com/CVE-2025-23027/index.md)","id":"CVE-2025-23027","markdown":"https://insights.sbomify.com/CVE-2025-23027/index.md","name":"CVE-2025-23027","record":{"aliases":["GHSA-wppx-qmqh-9h33"],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Next.js boilerplate","requires_auth":"none","summary":"Developers using the next-forge boilerplate must remove the hardcoded BASEHUB_TOKEN from example files to prevent unauthorized access to BaseHub services.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"next-forge is a Next.js project boilerplate for modern web application. The BASEHUB_TOKEN commited in apps/web/.env.example. Users should avoid use of this token and should remove any access it may have in their systems.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"BASEHUB_TOKEN commited in next-forge","id":"CVE-2025-23027","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"DoS in Cilium agent DNS proxy from crafted DNS responses","id":"CVE-2025-23028"},"packages":[],"prev":{"headline":"HTML templates containing Javascript template strings are subject to XSS in jte","id":"CVE-2025-23026"},"products":["next-forge"],"published":"2025-01-13","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-13","vendors":["haydenbleasel"]},"summary":"Developers using the next-forge boilerplate must remove the hardcoded BASEHUB_TOKEN from example files to prevent unauthorized access to BaseHub services.","url":"https://insights.sbomify.com/CVE-2025-23027/"}