{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-1661 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-1661 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1661 is a medium-severity cross-site scripting vulnerability in Unknown WP Mail Logging, published on 2 Oct 2026. 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-2026-1661 and fix it if it is affected.\n\nWhat it is: CVE-2026-1661 is a medium-severity cross-site scripting vulnerability in Unknown WP Mail Logging, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-1661 in the wild and no public exploit code.\n\nAffected product: Unknown 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-1661/ (Markdown: https://insights.sbomify.com/CVE-2026-1661/index.md)","id":"CVE-2026-1661","markdown":"https://insights.sbomify.com/CVE-2026-1661/index.md","name":"CVE-2026-1661","record":{"aliases":["GHSA-3mmj-c498-mq95"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject HTML into email logs to deceive administrators and redirect them to malicious sites.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WP Mail Logging WordPress plugin before 1.17.0 does not properly restrict the HTML and CSS of logged emails before rendering them in its admin log screens, allowing unauthenticated users to inject styled content and links, for example through a public contact form, that can deceive an administrator viewing the log and send their browser to an attacker-controlled page.","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":"WP Mail Logging \u003c 1.17.0 - Unauthenticated HTML Injection","id":"CVE-2026-1661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Allocation of Resources Without Limits or Throttling in GitLab","id":"CVE-2026-1662"},"packages":[],"prev":{"headline":"Allocation of Resources Without Limits or Throttling in GitLab","id":"CVE-2026-1660"},"products":["WP Mail Logging"],"published":"2026-10-02","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-02","vendors":["Unknown"]},"summary":"Unauthenticated attackers can inject HTML into email logs to deceive administrators and redirect them to malicious sites.","url":"https://insights.sbomify.com/CVE-2026-1661/"}