{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13505 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-13505 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13505 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Jul 2019. 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-2019-13505 and fix it if it is affected.\n\nWhat it is: CVE-2019-13505 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Jul 2019. 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-2019-13505 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-2019-13505/ (Markdown: https://insights.sbomify.com/CVE-2019-13505/index.md)","id":"CVE-2019-13505","markdown":"https://insights.sbomify.com/CVE-2019-13505/index.md","name":"CVE-2019-13505","record":{"aliases":["GHSA-j4gr-j44w-w9m4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Cross-site scripting vulnerability in Appointment Hour Booking plugin allows attackers to inject malicious scripts via the email field.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"appointment_hour_booking","vendor":"dwbooster"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"The Appointment Hour Booking plugin 1.1.44 for WordPress allows XSS via the E-mail field, as demonstrated by email_1.","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 scripting in n/a","id":"CVE-2019-13505","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-Site Scripting in @nuxt/devalue","id":"CVE-2019-13506"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-13504"},"products":["n/a"],"published":"2019-07-11","related":[{"cvss_score":7.2,"headline":"Appointment Hour Booking \u003c= 1.3.72 - Unauthenticated iFrame Injection via Appointment Form","id":"CVE-2022-4035","kev_date_added":null,"published":"2022-11-29"},{"cvss_score":5.8,"headline":"Appointment Hour Booking \u003c= 1.3.72 - CSV Injection","id":"CVE-2022-4034","kev_date_added":null,"published":"2022-11-29"},{"cvss_score":5.4,"headline":"Appointment Hour Booking – WordPress Booking Plugin \u003c 1.3.17 - Authenticated Stored XSS","id":"CVE-2021-24712","kev_date_added":null,"published":"2021-10-11"},{"cvss_score":5.3,"headline":"Appointment Hour Booking \u003c= 1.3.72 - CAPTCHA Bypass","id":"CVE-2022-4036","kev_date_added":null,"published":"2022-11-29"},{"cvss_score":4.8,"headline":"Appointment Hour Booking \u003c 1.3.56 - Admin+ Stored Cross-Site Scripting","id":"CVE-2022-1710","kev_date_added":null,"published":"2022-06-13"},{"cvss_score":4.8,"headline":"Appointment Hour Booking \u003c 1.3.16 - Authenticated Stored Cross-Site Scripting","id":"CVE-2021-24673","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":"Cross-site scripting vulnerability in Appointment Hour Booking plugin allows attackers to inject malicious scripts via the email field.","url":"https://insights.sbomify.com/CVE-2019-13505/"}