{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47003 exists.","fix":"No fix has been published for CVE-2022-47003 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-47003 is a critical authentication bypass vulnerability in n/a, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-47003 and fix it if it is affected.\n\nWhat it is: CVE-2022-47003 is a critical authentication bypass vulnerability in n/a, published on 1 Feb 2023. 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-2022-47003 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-2022-47003/ (Markdown: https://insights.sbomify.com/CVE-2022-47003/index.md)","id":"CVE-2022-47003","markdown":"https://insights.sbomify.com/CVE-2022-47003/index.md","name":"CVE-2022-47003","record":{"aliases":["GHSA-q3p4-9xc9-mmhf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mura CMS","requires_auth":"none","summary":"Attackers can bypass authentication in Mura CMS via a crafted request exploiting the Remember Me function.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mura_cms","vendor":"murasoftware"}],"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-287","name":"Improper Authentication"}],"description":"A vulnerability in the Remember Me function of Mura CMS before v10.0.580 allows attackers to bypass authentication via a crafted web request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-47003.yaml","stars":null,"title":"Mura CMS \u003c10.0.580 - Authentication Bypass"}],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2022-47003","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2022-47007"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2022-47002"},"products":["n/a"],"published":"2023-02-01","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-67829","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-67830","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55040","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55044","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":8.1,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55046","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55041","kev_date_added":null,"published":"2026-03-18"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"Attackers can bypass authentication in Mura CMS via a crafted request exploiting the Remember Me function.","url":"https://insights.sbomify.com/CVE-2022-47003/"}