{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3179 exists.","fix":"No fix has been published for CVE-2023-3179 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3179 is a high-severity vulnerability in Unknown POST SMTP Mailer, published on 17 Jul 2023. 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-2023-3179 and fix it if it is affected.\n\nWhat it is: CVE-2023-3179 is a high-severity vulnerability in Unknown POST SMTP Mailer, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3179 exists.\n\nAffected product: Unknown POST SMTP Mailer. 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-2023-3179/ (Markdown: https://insights.sbomify.com/CVE-2023-3179/index.md)","id":"CVE-2023-3179","markdown":"https://insights.sbomify.com/CVE-2023-3179/index.md","name":"CVE-2023-3179","record":{"aliases":["GHSA-6qcm-jr9r-5m65"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can exploit missing CSRF checks to force users to resend emails to attacker addresses, potentially leading to account takeover.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"post_smtp","vendor":"wpexperts"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The POST SMTP Mailer WordPress plugin before 2.5.7 does not have proper CSRF checks in some AJAX actions, which could allow attackers to make logged in users with the manage_postman_smtp capability resend an email to an arbitrary address (for example a password reset email could be resent to an attacker controlled email, and allow them to take over an account).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"POST SMTP Mailer \u003c 2.5.7 - Account Takeover via CSRF","id":"CVE-2023-3179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Heap buffer overflow in virtio_crypto_sym_op_helper()","id":"CVE-2023-3180"},"packages":[],"prev":{"headline":"POST SMTP Mailer \u003c 2.5.7 - Arbitrary Log Deletion via CSRF","id":"CVE-2023-3178"},"products":["POST SMTP Mailer"],"published":"2023-07-17","related":[{"cvss_score":9.8,"headline":"Auth bypass in Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP \u0026 Mobile App","id":"CVE-2023-6875","kev_date_added":null,"published":"2024-01-11"},{"cvss_score":8.6,"headline":"WordPress POST SMTP Mailer plugin \u003c= 2.8.6 - Broken Access Control on API vulnerability","id":"CVE-2023-52233","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":7.6,"headline":"WordPress Post SMTP plugin \u003c= 2.9.9 - SQL Injection vulnerability","id":"CVE-2024-52436","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":7.2,"headline":"Post SMTP \u003c= 3.0.2 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2025-0521","kev_date_added":null,"published":"2025-02-18"},{"cvss_score":7.2,"headline":"SQL injection in Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP \u0026 Mobile App","id":"CVE-2024-5207","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":7.2,"headline":"Post SMTP \u003c 2.8.7 - Admin+ SQL Injection","id":"CVE-2023-6620","kev_date_added":null,"published":"2024-01-15"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-07","vendors":["Unknown"]},"summary":"Attackers can exploit missing CSRF checks to force users to resend emails to attacker addresses, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2023-3179/"}