{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14348 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14348 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14348 is a medium-severity missing authorization vulnerability in wedevs weMail: Email Marketing, Email Automation, Newsletters, Subscribers \u0026 Email Optins for WooCommerce, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14348 and fix it if it is affected.\n\nWhat it is: CVE-2025-14348 is a medium-severity missing authorization vulnerability in wedevs weMail: Email Marketing, Email Automation, Newsletters, Subscribers \u0026 Email Optins for WooCommerce, published on 20 Jan 2026. 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-2025-14348 in the wild and no public exploit code.\n\nAffected product: wedevs weMail: Email Marketing, Email Automation, Newsletters, Subscribers \u0026 Email Optins for WooCommerce. 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-2025-14348/ (Markdown: https://insights.sbomify.com/CVE-2025-14348/index.md)","id":"CVE-2025-14348","markdown":"https://insights.sbomify.com/CVE-2025-14348/index.md","name":"CVE-2025-14348","record":{"aliases":["GHSA-hxqm-jx76-mpgf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authorization via a spoofed header to access sensitive subscriber PII in the weMail WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"The weMail - Email Marketing, Lead Generation, Optin Forms, Email Newsletters, A/B Testing, and Automation plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.0.7. This is due to the plugin's REST API trusting the `x-wemail-user` HTTP header to identify users without verifying the request originates from an authenticated WordPress session. This makes it possible for unauthenticated attackers who know or can guess an admin email (easily enumerable via `/wp-json/wp/v2/users`) to impersonate that user and access the CSV subscriber endpoints, potentially exfiltrating subscriber PII (emails, names, phone numbers) from imported CSV files.","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":"weMail \u003c= 2.0.7 - Insufficient Authorization via x-wemail-user Header to Sensitive Information Disclosure","id":"CVE-2025-14348","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Business Logic Error in Universal Software's FlexCity/Kiosk","id":"CVE-2025-14349"},"packages":[],"prev":{"headline":"Reflected XSS in Proliz's OBS","id":"CVE-2025-14347"},"products":["weMail: Email Marketing, Email Automation, Newsletters, Subscribers \u0026 Email Optins for WooCommerce"],"published":"2026-01-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["wedevs"]},"summary":"Unauthenticated attackers can bypass authorization via a spoofed header to access sensitive subscriber PII in the weMail WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-14348/"}