{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15106 exists.","fix":"No fix has been published for CVE-2025-15106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15106 is a medium-severity missing authorization vulnerability in getmaxun maxun, published on 27 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-15106 and fix it if it is affected.\n\nWhat it is: CVE-2025-15106 is a medium-severity missing authorization vulnerability in getmaxun maxun, published on 27 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15106 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-15106/ (Markdown: https://insights.sbomify.com/CVE-2025-15106/index.md)","id":"CVE-2025-15106","markdown":"https://insights.sbomify.com/CVE-2025-15106/index.md","name":"CVE-2025-15106","record":{"aliases":["GHSA-72f9-ghc4-fpv2"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"maxun authentication endpoint","requires_auth":"low_privilege","summary":"Remote attackers can bypass authorization checks in the maxun authentication endpoint due to improper access control in the router.get function.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"maxun","vendor":"maxun"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A weakness has been identified in getmaxun maxun up to 0.0.28. The affected element is the function router.get of the file server/src/routes/auth.ts of the component Authentication Endpoint. Executing manipulation can lead to improper authorization. The attack can be executed remotely. The exploit has been made available to the public and could 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 Authentication Endpoint auth.ts router.get improper authorization","id":"CVE-2025-15106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"actiontech sqle JWT Secret jwt.go hard-coded key","id":"CVE-2025-15107"},"packages":[],"prev":{"headline":"getmaxun auth.ts hard-coded key","id":"CVE-2025-15105"},"products":["maxun"],"published":"2025-12-27","related":[{"cvss_score":6.3,"headline":"getmaxun auth.ts hard-coded key","id":"CVE-2025-15105","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-29","vendors":["getmaxun"]},"summary":"Remote attackers can bypass authorization checks in the maxun authentication endpoint due to improper access control in the router.get function.","url":"https://insights.sbomify.com/CVE-2025-15106/"}