{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11141 exists.","fix":"No fix has been published for CVE-2024-11141 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11141 is a medium-severity cross-site scripting vulnerability in Unknown Sailthru Triggermail, published on 15 May 2025. 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-2024-11141 and fix it if it is affected.\n\nWhat it is: CVE-2024-11141 is a medium-severity cross-site scripting vulnerability in Unknown Sailthru Triggermail, published on 15 May 2025. 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-2024-11141 exists.\n\nAffected product: Unknown Sailthru Triggermail. 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-2024-11141/ (Markdown: https://insights.sbomify.com/CVE-2024-11141/index.md)","id":"CVE-2024-11141","markdown":"https://insights.sbomify.com/CVE-2024-11141/index.md","name":"CVE-2024-11141","record":{"aliases":["GHSA-874p-6rxv-4ppg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Subscribers can inject malicious scripts via unsanitized settings in the Sailthru Triggermail WordPress plugin, bypassing standard HTML filtering protections.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"sailthru_triggermail","vendor":"jontasc"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Sailthru Triggermail WordPress plugin through 1.1 does not sanitise and escape some of its settings and is missing CSRF protection which could allow subscribers to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Sailthru Triggermail \u003c 1.1 - Subscriber+ Stored XSS","id":"CVE-2024-11141","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"CSRF in Gosoft Software's Proticaret E-Commerce","id":"CVE-2024-11142"},"packages":[],"prev":{"headline":"Real WP Shop Lite Ajax eCommerce Shopping Cart \u003c= 2.0.8 - Admin+ Stored XSS","id":"CVE-2024-11140"},"products":["Sailthru Triggermail"],"published":"2025-05-15","related":[{"cvss_score":7.1,"headline":"Sailthru Triggermail \u003c= 1.1 - Admin+ Stored XSS","id":"CVE-2024-4290","kev_date_added":null,"published":"2024-05-21"},{"cvss_score":6.1,"headline":"Sailthru Triggermail \u003c= 1.1 - Reflected XSS","id":"CVE-2024-4289","kev_date_added":null,"published":"2024-05-21"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-05-20","vendors":["Unknown"]},"summary":"Subscribers can inject malicious scripts via unsanitized settings in the Sailthru Triggermail WordPress plugin, bypassing standard HTML filtering protections.","url":"https://insights.sbomify.com/CVE-2024-11141/"}