{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15330 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15330 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15330 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15330 and fix it if it is affected.\n\nWhat it is: CVE-2019-15330 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2019. 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-2019-15330 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-15330/ (Markdown: https://insights.sbomify.com/CVE-2019-15330/index.md)","id":"CVE-2019-15330","markdown":"https://insights.sbomify.com/CVE-2019-15330/index.md","name":"CVE-2019-15330","record":{"aliases":["GHSA-hq9w-4h7q-x8qw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can read arbitrary files from the server via the webp-express WordPress plugin due to insufficient protection against path traversal.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"webp_express","vendor":"webp_express_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[],"description":"The webp-express plugin before 0.14.11 for WordPress has insufficient protection against arbitrary file reading.","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":"Path traversal in n/a","id":"CVE-2019-15330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-15331"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-15329"},"products":["n/a"],"published":"2019-08-22","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can read arbitrary files from the server via the webp-express WordPress plugin due to insufficient protection against path traversal.","url":"https://insights.sbomify.com/CVE-2019-15330/"}