{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2370 is a medium-severity missing authorization vulnerability in Unknown YaySMTP, published on 1 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-2370 and fix it if it is affected.\n\nWhat it is: CVE-2022-2370 is a medium-severity missing authorization vulnerability in Unknown YaySMTP, published on 1 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-2370 in the wild and no public exploit code.\n\nAffected product: Unknown YaySMTP. 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-2022-2370/ (Markdown: https://insights.sbomify.com/CVE-2022-2370/index.md)","id":"CVE-2022-2370","markdown":"https://insights.sbomify.com/CVE-2022-2370/index.md","name":"CVE-2022-2370","record":{"aliases":["GHSA-7vqg-r6cw-6w76"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can retrieve SMTP credentials due to missing capability checks in the YaySMTP WordPress plugin settings.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"yaysmtp","vendor":"yaycommerce"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The YaySMTP WordPress plugin before 2.2.1 does not have capability check before displaying the Mailer Credentials in JS code for the settings, allowing any authenticated users, such as subscriber to retrieve them","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":"YaySMTP \u003c 2.2.1 - Subscriber+ SMTP Credentials Leak","id":"CVE-2022-2370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"YaySMTP \u003c 2.2.1 - Subscriber+ Stored Cross-Site Scripting","id":"CVE-2022-2371"},"packages":[],"prev":{"headline":"YaySMTP \u003c 2.2.1 - Subscriber+ Logs Disclosure","id":"CVE-2022-2369"},"products":["YaySMTP"],"published":"2022-08-01","related":[{"cvss_score":7.2,"headline":"SMTP for SendGrid – YaySMTP \u003c= 1.4 - Unauthenticated Stored Cross-Site Scripting via Email Logs","id":"CVE-2025-0918","kev_date_added":null,"published":"2025-02-22"},{"cvss_score":7.2,"headline":"SMTP for Sendinblue – YaySMTP \u003c= 1.2 - Unauthenticated Stored Cross-Site Scripting via Email Logs","id":"CVE-2025-0953","kev_date_added":null,"published":"2025-02-22"},{"cvss_score":7.2,"headline":"YaySMTP 2.4.9 - 2.6.2 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2025-0916","kev_date_added":null,"published":"2025-02-19"},{"cvss_score":7.2,"headline":"YaySMTP \u003c= 2.4.5 - Unauthenticated Stored Cross-Site Scripting via Email","id":"CVE-2023-3093","kev_date_added":null,"published":"2023-07-12"},{"cvss_score":5.4,"headline":"YaySMTP \u003c 2.2.1 - Subscriber+ Stored Cross-Site Scripting","id":"CVE-2022-2371","kev_date_added":null,"published":"2022-08-08"},{"cvss_score":4.8,"headline":"YaySMTP \u003c 2.2.2 - Admin+ Stored Cross-Site Scripting","id":"CVE-2022-2372","kev_date_added":null,"published":"2022-08-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-03","vendors":["Unknown"]},"summary":"Authenticated subscribers can retrieve SMTP credentials due to missing capability checks in the YaySMTP WordPress plugin settings.","url":"https://insights.sbomify.com/CVE-2022-2370/"}