{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1617 exists.","fix":"No fix has been published for CVE-2022-1617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1617 is a medium-severity cross-site scripting vulnerability in Unknown WP-Invoice, published on 16 Jan 2024. 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-2022-1617 and fix it if it is affected.\n\nWhat it is: CVE-2022-1617 is a medium-severity cross-site scripting vulnerability in Unknown WP-Invoice, published on 16 Jan 2024. 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-2022-1617 exists.\n\nAffected product: Unknown WP-Invoice. 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-2022-1617/ (Markdown: https://insights.sbomify.com/CVE-2022-1617/index.md)","id":"CVE-2022-1617","markdown":"https://insights.sbomify.com/CVE-2022-1617/index.md","name":"CVE-2022-1617","record":{"aliases":["GHSA-qp39-g94h-cxxf"],"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":"Attackers can inject malicious scripts into WP-Invoice settings via CSRF, leading to code execution in the admin context.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp-invoice","vendor":"usabilitydynamics"}],"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-352","name":"Cross-Site Request Forgery"}],"description":"The WP-Invoice WordPress plugin through 4.3.1 does not have CSRF check in place when updating its settings, and is lacking sanitisation as well as escaping in some of them, allowing attacker to make a logged in admin change them and add XSS payload in them","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":"WP-Invoice \u003c= 4.3.1 - Stored Cross-Site Scripting via CSRF","id":"CVE-2022-1617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Coru LFMember \u003c= 1.0.2 - Stored Cross-Site Scripting via CSRF","id":"CVE-2022-1618"},"packages":[],"prev":{"headline":"Use after free in append_command in vim/vim","id":"CVE-2022-1616"},"products":["WP-Invoice"],"published":"2024-01-16","related":[{"cvss_score":6.5,"headline":"Privilege escalation in n/a","id":"CVE-2016-11011","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2016-11006","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2016-11007","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_paypal payer metadata updates.","id":"CVE-2016-11008","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_interkassa payer metadata updates.","id":"CVE-2016-11009","kev_date_added":null,"published":"2019-09-20"},{"cvss_score":5.3,"headline":"The wp-invoice plugin before 4.1.1 for WordPress has incorrect access control over wpi_twocheckout payer metadata updates.","id":"CVE-2016-11010","kev_date_added":null,"published":"2019-09-20"}],"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-06-11","vendors":["Unknown"]},"summary":"Attackers can inject malicious scripts into WP-Invoice settings via CSRF, leading to code execution in the admin context.","url":"https://insights.sbomify.com/CVE-2022-1617/"}