{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-9371 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-9371 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-9371 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Mar 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-9371 and fix it if it is affected.\n\nWhat it is: CVE-2020-9371 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Mar 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-9371 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-9371/ (Markdown: https://insights.sbomify.com/CVE-2020-9371/index.md)","id":"CVE-2020-9371","markdown":"https://insights.sbomify.com/CVE-2020-9371/index.md","name":"CVE-2020-9371","record":{"aliases":["GHSA-857r-rchh-235h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Attackers can inject arbitrary JavaScript via the Calendar Name input in the Appointment Booking Calendar plugin, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"appointment_booking_calendar","vendor":"codepeople"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Stored XSS exists in the Appointment Booking Calendar plugin before 1.3.35 for WordPress. In the cpabc_appointments.php file, the Calendar Name input could allow attackers to inject arbitrary JavaScript or HTML.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2020-03-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-03-12","kind":"exploitdb","ref":"48204","stars":null,"title":"WordPress Plugin Appointment Booking Calendar 1.3.34 - CSV Injection"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2020-9371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":5,"next":{"headline":"Code injection in n/a","id":"CVE-2020-9372"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-9370"},"products":["n/a"],"published":"2020-03-04","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2016-10916","kev_date_added":null,"published":"2019-08-22"},{"cvss_score":8.8,"headline":"Booking Calendar \u003c 1.3.83 - CSRF appointment scheduling","id":"CVE-2024-0856","kev_date_added":null,"published":"2024-03-20"},{"cvss_score":8.2,"headline":"WordPress Appointment Booking Calendar plugin \u003c= 1.3.92 - CSRF to SQL Injection vulnerability","id":"CVE-2025-46241","kev_date_added":null,"published":"2025-04-22"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2020-9372","kev_date_added":null,"published":"2020-03-04"},{"cvss_score":7.5,"headline":"BookingPress \u003c 1.1.23 - Unauthenticated Export File Download","id":"CVE-2024-12274","kev_date_added":null,"published":"2025-01-13"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2015-7319","kev_date_added":null,"published":"2015-09-29"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-14791","kev_date_added":null,"published":"2019-08-09"}],"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":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can inject arbitrary JavaScript via the Calendar Name input in the Appointment Booking Calendar plugin, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2020-9371/"}