{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-25145 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-25145 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-25145 is a high-severity cross-site scripting vulnerability in smub Contact Form \u0026 SMTP Plugin for WordPress by PirateForms, published on 7 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25145 and fix it if it is affected.\n\nWhat it is: CVE-2019-25145 is a high-severity cross-site scripting vulnerability in smub Contact Form \u0026 SMTP Plugin for WordPress by PirateForms, published on 7 Jun 2023. 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-2019-25145 in the wild and no public exploit code.\n\nAffected product: smub Contact Form \u0026 SMTP Plugin for WordPress by PirateForms. 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-2019-25145/ (Markdown: https://insights.sbomify.com/CVE-2019-25145/index.md)","id":"CVE-2019-25145","markdown":"https://insights.sbomify.com/CVE-2019-25145/index.md","name":"CVE-2019-25145","record":{"aliases":["GHSA-mcgq-qxvq-33gm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary HTML into emails via the PirateForms plugin, enabling phishing attacks against victims.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"contact_form","vendor":"wpforms"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Contact Form \u0026 SMTP Plugin by PirateForms plugin for WordPress is vulnerable to HTML injection in the ‘public/class-pirateforms-public.php’ file in versions up to, and including, 2.5.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary HTML in emails that could be used to phish unsuspecting victims.","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":"Contact Form \u0026 SMTP Plugin by PirateForms \u003c= 2.5.1 - Unauthenticated HTML injection","id":"CVE-2019-25145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"DELUCKS SEO \u003c 2.1.8 - Stored Cross Site Scripting","id":"CVE-2019-25146"},"packages":[],"prev":{"headline":"WP HTML Mail \u003c 2.2.11 - HTML injection","id":"CVE-2019-25144"},"products":["Contact Form \u0026 SMTP Plugin for WordPress by PirateForms"],"published":"2023-06-07","related":[{"cvss_score":6.1,"headline":"Contact Form \u0026 SMTP Plugin for WordPress by PirateForms \u003c 2.6.0 - Admin+ Stored XSS","id":"CVE-2024-11273","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":5.8,"headline":"WordPress WPForms plugins - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2023-30500","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-10385","kev_date_added":null,"published":"2020-03-11"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["smub"]},"summary":"Unauthenticated attackers can inject arbitrary HTML into emails via the PirateForms plugin, enabling phishing attacks against victims.","url":"https://insights.sbomify.com/CVE-2019-25145/"}