{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-31745 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-31745 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-31745 is a high-severity authentication bypass vulnerability in n/a, published on 10 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-31745 and fix it if it is affected.\n\nWhat it is: CVE-2021-31745 is a high-severity authentication bypass vulnerability in n/a, published on 10 Dec 2021. 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-2021-31745 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-2021-31745/ (Markdown: https://insights.sbomify.com/CVE-2021-31745/index.md)","id":"CVE-2021-31745","markdown":"https://insights.sbomify.com/CVE-2021-31745/index.md","name":"CVE-2021-31745","record":{"aliases":["GHSA-prm5-542j-m494"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Pluck CMS","requires_auth":"none","summary":"Attackers can maintain unauthorized access to Pluck CMS after password changes due to lack of session invalidation, requiring administrators to patch the application.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pluck","vendor":"pluck-cms"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","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-384","name":"Session Fixation"}],"description":"Session Fixation vulnerability in login.php in Pluck-CMS Pluck 4.7.15 allows an attacker to sustain unauthorized access to the platform. Because Pluck does not invalidate prior sessions after a password change, access can be sustained even after an administrator performs regular remediation attempts such as resetting their password.","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-2021-31745","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2021-31746"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-31740"},"products":["n/a"],"published":"2021-12-10","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2024-43042","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2021-31746","kev_date_added":null,"published":"2021-12-10"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-20951","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2019-11344","kev_date_added":null,"published":"2019-04-19"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2018-11736","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2018-11331","kev_date_added":null,"published":"2018-05-21"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2014-8708","kev_date_added":null,"published":"2017-03-17"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can maintain unauthorized access to Pluck CMS after password changes due to lack of session invalidation, requiring administrators to patch the application.","url":"https://insights.sbomify.com/CVE-2021-31745/"}