{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-109401 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-109401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-109401 is a low-severity vulnerability in smub WP Mail Logging, published on 16 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-109401 and fix it if it is affected.\n\nWhat it is: CVE-2026-109401 is a low-severity vulnerability in smub WP Mail Logging, published on 16 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-109401 in the wild and no public exploit code.\n\nAffected product: smub WP Mail Logging. 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-2026-109401/ (Markdown: https://insights.sbomify.com/CVE-2026-109401/index.md)","id":"CVE-2026-109401","markdown":"https://insights.sbomify.com/CVE-2026-109401/index.md","name":"CVE-2026-109401","record":{"aliases":["GHSA-wv84-f6wm-rwxx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Administrators can expose other users' logged email data via wildcard injection in personal data exports, requiring immediate plugin updates.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The WP Mail Logging plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.17.0 via the 'email_address' parameter. This makes it possible for authenticated attackers, with administrator-level access and above, to extract complete logged mail rows belonging to other users — including recipient addresses, message subjects, full message bodies, and any URLs contained therein — whose addresses happen to match the wildcard. Exploitation requires an administrator to process a personal-data export request for the attacker's email address via the standard WordPress privacy workflow, and the attacker's address must contain a LIKE wildcard character (such as an underscore) that matches at least one other user's address in the mail log.","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 WP Mail Logging","id":"CVE-2026-109401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"conductor-oss conductor MCP Service MCPService.java MCPService.listTools server-side request forgery","id":"CVE-2026-109402"},"packages":[],"prev":{"headline":"Privilege escalation in InstaWP Connect – 1-click WP Staging \u0026 Migration","id":"CVE-2026-109400"},"products":["WP Mail Logging"],"published":"2026-10-16","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["smub"]},"summary":"Administrators can expose other users' logged email data via wildcard injection in personal data exports, requiring immediate plugin updates.","url":"https://insights.sbomify.com/CVE-2026-109401/"}