{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-48176 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-48176 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-48176 is a critical authentication bypass vulnerability in n/a, published on 5 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-48176 and fix it if it is affected.\n\nWhat it is: CVE-2024-48176 is a critical authentication bypass vulnerability in n/a, published on 5 Nov 2024. 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-2024-48176 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2024-48176/ (Markdown: https://insights.sbomify.com/CVE-2024-48176/index.md)","id":"CVE-2024-48176","markdown":"https://insights.sbomify.com/CVE-2024-48176/index.md","name":"CVE-2024-48176","record":{"aliases":["GHSA-cjhr-gw79-v8fh"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Lylme Spage","requires_auth":"none","summary":"Attackers can brute-force login credentials due to missing attempt limits and static verification codes, gaining unauthorized backend access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lylme_spage","vendor":"lylme"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Lylme Spage v1.9.5 is vulnerable to Incorrect Access Control. There is no limit on the number of login attempts, and the verification code will not be refreshed after a failed login, which allows attackers to blast the username and password and log into the system backend.","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 n/a","id":"CVE-2024-48176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2024-48177"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-48170"},"products":["n/a"],"published":"2024-11-05","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48356","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48357","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-34982","kev_date_added":null,"published":"2024-05-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-45951","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-45952","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2024-36675","kev_date_added":null,"published":"2024-06-04"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-06","vendors":["n/a"]},"summary":"Attackers can brute-force login credentials due to missing attempt limits and static verification codes, gaining unauthorized backend access.","url":"https://insights.sbomify.com/CVE-2024-48176/"}