{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-33319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-33319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-33319 is a high-severity cross-site scripting vulnerability in WooCommerce Follow-Up Emails (AutomateWoo), published on 28 May 2023. 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-2023-33319 and fix it if it is affected.\n\nWhat it is: CVE-2023-33319 is a high-severity cross-site scripting vulnerability in WooCommerce Follow-Up Emails (AutomateWoo), published on 28 May 2023. 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-2023-33319 in the wild and no public exploit code.\n\nAffected product: WooCommerce Follow-Up Emails (AutomateWoo). 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-2023-33319/ (Markdown: https://insights.sbomify.com/CVE-2023-33319/index.md)","id":"CVE-2023-33319","markdown":"https://insights.sbomify.com/CVE-2023-33319/index.md","name":"CVE-2023-33319","record":{"aliases":["GHSA-9vw6-9gf6-x43j"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject malicious scripts via reflected XSS in the WooCommerce Follow-Up Emails plugin, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"automatewoo","vendor":"woocommerce"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in WooCommerce WooCommerce Follow-Up Emails (AutomateWoo) plugin \u003c= 4.9.40 versions.","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":"WordPress WooCommerce Follow-Up Emails Plugin \u003c= 4.9.40 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-33319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress WP-Hijri Plugin \u003c= 1.5.1 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-33320"},"packages":[],"prev":{"headline":"WordPress WooCommerce Follow-Up Emails Plugin \u003c= 4.9.40 is vulnerable to Arbitrary File Upload","id":"CVE-2023-33318"},"products":["WooCommerce Follow-Up Emails (AutomateWoo)"],"published":"2023-05-28","related":[{"cvss_score":9.9,"headline":"WordPress WooCommerce Follow-Up Emails Plugin \u003c= 4.9.40 is vulnerable to Arbitrary File Upload","id":"CVE-2023-33318","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":8.5,"headline":"WordPress WooCommerce Follow-Up Emails Plugin \u003c= 4.9.50 is vulnerable to SQL Injection","id":"CVE-2023-33330","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":7.6,"headline":"WordPress AutomateWoo Plugin \u003c= 5.7.1 is vulnerable to SQL Injection","id":"CVE-2023-32743","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":5.4,"headline":"WordPress AutomateWoo Plugin \u003c= 5.7.1 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-32745","kev_date_added":null,"published":"2023-11-09"},{"cvss_score":5.4,"headline":"WordPress AutomateWoo Plugin \u003c= 5.7.5 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-36513","kev_date_added":null,"published":"2023-07-17"},{"cvss_score":5.4,"headline":"Cross-site request forgery in WooCommerce Follow-Up Emails (AutomateWoo)","id":"CVE-2023-33316","kev_date_added":null,"published":"2023-05-28"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["WooCommerce"]},"summary":"Unauthenticated attackers can inject malicious scripts via reflected XSS in the WooCommerce Follow-Up Emails plugin, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2023-33319/"}