{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27379 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-27379 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27379 is a medium-severity vulnerability in n/a, published on 14 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-27379 and fix it if it is affected.\n\nWhat it is: CVE-2020-27379 is a medium-severity vulnerability in n/a, published on 14 Jul 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-27379 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-2020-27379/ (Markdown: https://insights.sbomify.com/CVE-2020-27379/index.md)","id":"CVE-2020-27379","markdown":"https://insights.sbomify.com/CVE-2020-27379/index.md","name":"CVE-2020-27379","record":{"aliases":["GHSA-r8c4-3mh9-m9p5"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Booking Core plugin","requires_auth":"none","summary":"Attackers can change user email via CSRF to reset passwords and take over accounts in Booking Core.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"booking_core","vendor":"bookingcore"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross Site Request Forgery (CSRF) vulnerability in Booking Core - Ultimate Booking System Booking Core 1.7.0 . The CSRF token is not being validated when the request is sent as a GET method. This results in an unauthorized change in the user's email ID, which can later be used to reset the password. The new password will be sent to a modified email ID.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-27379","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-27383"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-27377"},"products":["n/a"],"published":"2021-07-14","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2021-37333","kev_date_added":null,"published":"2021-10-04"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2020-25445","kev_date_added":null,"published":"2021-07-14"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2021-37330","kev_date_added":null,"published":"2021-10-04"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-25444","kev_date_added":null,"published":"2021-07-14"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2021-37331","kev_date_added":null,"published":"2021-10-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can change user email via CSRF to reset passwords and take over accounts in Booking Core.","url":"https://insights.sbomify.com/CVE-2020-27379/"}