{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6015 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6015 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6015 is a high-severity vulnerability in n/a, published on 26 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6015 and fix it if it is affected.\n\nWhat it is: CVE-2018-6015 is a high-severity vulnerability in n/a, published on 26 Jan 2018. 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-2018-6015 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-2018-6015/ (Markdown: https://insights.sbomify.com/CVE-2018-6015/index.md)","id":"CVE-2018-6015","markdown":"https://insights.sbomify.com/CVE-2018-6015/index.md","name":"CVE-2018-6015","record":{"aliases":["GHSA-8776-7wq4-2rcx"],"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 download all subscriber data via a crafted HTTP POST request, exposing sensitive user information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"email_subscribers_\\\u0026_newsletters","vendor":"icegram"}],"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":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in the \"Email Subscribers \u0026 Newsletters\" plugin before 3.4.8 for WordPress. Sending an HTTP POST request to a URI with /?es=export at the end, and adding option=view_all_subscribers in the body, allows downloading of a CSV data file with all subscriber data.","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":"Information disclosure in n/a","id":"CVE-2018-6015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2018-6016"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-6014"},"products":["n/a"],"published":"2018-01-26","related":[{"cvss_score":9.8,"headline":"SQL injection in Email Subscribers \u0026 Newsletters – Email Marketing, Post Notifications \u0026 Newsletter Plugin for WordPress","id":"CVE-2024-6172","kev_date_added":null,"published":"2024-07-02"},{"cvss_score":9.8,"headline":"Email Subscribers by Icegram Express \u003c= 5.7.20 - Unauthenticated SQL Injection via hash","id":"CVE-2024-4295","kev_date_added":null,"published":"2024-06-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13569","kev_date_added":null,"published":"2019-07-19"},{"cvss_score":8.8,"headline":"Icegram Express \u003c 5.5.1 - Subscriber+ SQLi","id":"CVE-2022-3981","kev_date_added":null,"published":"2022-12-12"},{"cvss_score":8.8,"headline":"Email Subscribers \u0026 Newsletters \u003c 5.3.2 - Subscriber+ Blind SQL injection","id":"CVE-2022-0439","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.3,"headline":"SQL injection in n/a","id":"CVE-2019-20361","kev_date_added":null,"published":"2020-01-08"}],"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":"An attacker can download all subscriber data via a crafted HTTP POST request, exposing sensitive user information.","url":"https://insights.sbomify.com/CVE-2018-6015/"}