{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19540 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19540 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19540 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Dec 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-19540 and fix it if it is affected.\n\nWhat it is: CVE-2019-19540 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Dec 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-19540 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-19540/ (Markdown: https://insights.sbomify.com/CVE-2019-19540/index.md)","id":"CVE-2019-19540","markdown":"https://insights.sbomify.com/CVE-2019-19540/index.md","name":"CVE-2019-19540","record":{"aliases":["GHSA-68pc-q3p4-jwvh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress theme","requires_auth":"none","summary":"Reflected XSS in ListingPro theme allows attackers to inject scripts via the What field, potentially leading to session hijacking or malicious actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"listingpro","vendor":"cridio"}],"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 ListingPro theme before v2.0.14.2 for WordPress has Reflected XSS via the What field on the homepage.","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-19540","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19541"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-19539"},"products":["n/a"],"published":"2019-12-26","related":[{"cvss_score":9.8,"headline":"ListingPro - WordPress Directory \u0026 Listing Theme \u003c 2.6.1 - Arbitrary Plugin Installation, Activation and Deactivation","id":"CVE-2020-36719","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":9.3,"headline":"WordPress ListingPro plugin \u003c= 2.9.4 - Unauthenticated SQL Injection vulnerability","id":"CVE-2024-38795","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":9.3,"headline":"WordPress ListingPro theme \u003c= 2.9.4 - Unauthenticated SQL Injection vulnerability","id":"CVE-2024-39622","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":9,"headline":"WordPress ListingPro plugin \u003c= 2.9.4 - Unauthenticated Local File Inclusion vulnerability","id":"CVE-2024-39619","kev_date_added":null,"published":"2024-08-01"},{"cvss_score":8.8,"headline":"WordPress ListingPro theme \u003c= 2.9.4 - Cross Site Request Forgery (CSRF) to Account Takeover vulnerability","id":"CVE-2024-39623","kev_date_added":null,"published":"2025-01-02"},{"cvss_score":8.5,"headline":"WordPress ListingPro plugin \u003c= 2.9.4 - SQL Injection vulnerability","id":"CVE-2024-39620","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":8.5,"headline":"WordPress ListingPro theme \u003c= 2.9.4 - Local File Inclusion vulnerability","id":"CVE-2024-39624","kev_date_added":null,"published":"2024-08-01"}],"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-05","vendors":["n/a"]},"summary":"Reflected XSS in ListingPro theme allows attackers to inject scripts via the What field, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2019-19540/"}