{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-55138 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55138 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55138 is a high-severity authentication bypass vulnerability in Latkecrszy LinkJoin, published on 7 Aug 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-55138 and fix it if it is affected.\n\nWhat it is: CVE-2025-55138 is a high-severity authentication bypass vulnerability in Latkecrszy LinkJoin, published on 7 Aug 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-55138 in the wild and no public exploit code.\n\nAffected product: Latkecrszy LinkJoin. 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-55138/ (Markdown: https://insights.sbomify.com/CVE-2025-55138/index.md)","id":"CVE-2025-55138","markdown":"https://insights.sbomify.com/CVE-2025-55138/index.md","name":"CVE-2025-55138","record":{"aliases":["GHSA-3vxm-73wh-v829"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"LinkJoin application","requires_auth":"none","summary":"Attackers can bypass password reset token ownership checks to take over user accounts in LinkJoin.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-304","name":"Missing Critical Step in Authentication"}],"description":"LinkJoin through 882f196 mishandles token ownership in password reset.","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":"Auth bypass in LinkJoin","id":"CVE-2025-55138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in Connect Secure","id":"CVE-2025-55139"},"packages":[],"prev":{"headline":"Business logic in LinkJoin","id":"CVE-2025-55137"},"products":["LinkJoin"],"published":"2025-08-07","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":"total"},"state":"PUBLISHED","updated":"2025-08-07","vendors":["Latkecrszy"]},"summary":"Attackers can bypass password reset token ownership checks to take over user accounts in LinkJoin.","url":"https://insights.sbomify.com/CVE-2025-55138/"}