{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15105 exists.","fix":"No fix has been published for CVE-2025-15105 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15105 is a medium-severity vulnerability in getmaxun maxun, published on 27 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-15105 and fix it if it is affected.\n\nWhat it is: CVE-2025-15105 is a medium-severity vulnerability in getmaxun maxun, published on 27 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-15105 exists.\n\nAffected product: getmaxun maxun. 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-15105/ (Markdown: https://insights.sbomify.com/CVE-2025-15105/index.md)","id":"CVE-2025-15105","markdown":"https://insights.sbomify.com/CVE-2025-15105/index.md","name":"CVE-2025-15105","record":{"aliases":["GHSA-9m78-g4jr-6549"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Maxun web application","requires_auth":"none","summary":"Attackers can exploit a hard-coded cryptographic key in the authentication module to bypass security controls in the Maxun web application.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"maxun","vendor":"maxun"}],"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-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"description":"A security flaw has been discovered in getmaxun maxun up to 0.0.28. Impacted is an unknown function of the file /getmaxun/maxun/blob/develop/server/src/routes/auth.ts. Performing manipulation of the argument api_key results in use of hard-coded cryptographic key\r . Remote exploitation of the attack is possible. The attack is considered to have high complexity. The exploitability is considered difficult. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.","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":"getmaxun auth.ts hard-coded key","id":"CVE-2025-15105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"getmaxun Authentication Endpoint auth.ts router.get improper authorization","id":"CVE-2025-15106"},"packages":[],"prev":{"headline":"Nu Html Checker (validator.nu) - Restriction bypass vulnerability allowing local SSRF","id":"CVE-2025-15104"},"products":["maxun"],"published":"2025-12-27","related":[{"cvss_score":5.3,"headline":"getmaxun Authentication Endpoint auth.ts router.get improper authorization","id":"CVE-2025-15106","kev_date_added":null,"published":"2025-12-27"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-29","vendors":["getmaxun"]},"summary":"Attackers can exploit a hard-coded cryptographic key in the authentication module to bypass security controls in the Maxun web application.","url":"https://insights.sbomify.com/CVE-2025-15105/"}