{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33329 exists.","fix":"No fix has been published for CVE-2024-33329 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-33329 is a high-severity vulnerability in n/a, published on 26 Jun 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-33329 and fix it if it is affected.\n\nWhat it is: CVE-2024-33329 is a high-severity vulnerability in n/a, published on 26 Jun 2024. 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-2024-33329 exists.\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-33329/ (Markdown: https://insights.sbomify.com/CVE-2024-33329/index.md)","id":"CVE-2024-33329","markdown":"https://insights.sbomify.com/CVE-2024-33329/index.md","name":"CVE-2024-33329","record":{"aliases":["GHSA-v3rc-5q86-wwq8"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Lumisxp web application","requires_auth":"none","summary":"Attackers can bypass authentication using a hardcoded privileged ID to access internal pages and sensitive information in Lumisxp.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"A hardcoded privileged ID within Lumisxp v15.0.x to v16.1.x allows attackers to bypass authentication and access internal pages and other sensitive information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-33329","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2024-33332"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-33328"},"products":["n/a"],"published":"2024-06-26","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-13","vendors":["n/a"]},"summary":"Attackers can bypass authentication using a hardcoded privileged ID to access internal pages and sensitive information in Lumisxp.","url":"https://insights.sbomify.com/CVE-2024-33329/"}