{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2171 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2171 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2171 is a medium-severity cross-site scripting vulnerability in Unknown Progressive License, published on 1 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-2171 and fix it if it is affected.\n\nWhat it is: CVE-2022-2171 is a medium-severity cross-site scripting vulnerability in Unknown Progressive License, published on 1 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-2171 in the wild and no public exploit code.\n\nAffected product: Unknown Progressive License. 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-2171/ (Markdown: https://insights.sbomify.com/CVE-2022-2171/index.md)","id":"CVE-2022-2171","markdown":"https://insights.sbomify.com/CVE-2022-2171/index.md","name":"CVE-2022-2171","record":{"aliases":["GHSA-j2wv-pvcq-h7hf"],"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":"low_privilege","summary":"Attackers can exploit CSRF to inject malicious HTML into settings, leading to Stored XSS that executes in the frontend.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"progressive_license","vendor":"crowdfavorite"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the settings, this could lead to Stored XSS issue which will be triggered in the frontend as well.","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":"Progressive License \u003c= 1.1.0 - CSRF to Stored XSS","id":"CVE-2022-2171","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"LinkWorth Plugin \u003c 3.3.4 - Arbitrary Setting Update via CSRF","id":"CVE-2022-2172"},"packages":[],"prev":{"headline":"Microsoft Advertising Universal Event Tracking \u003c 1.0.4 - Admin+ Stored Cross-Site Scripting","id":"CVE-2022-2170"},"products":["Progressive License"],"published":"2022-08-01","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Attackers can exploit CSRF to inject malicious HTML into settings, leading to Stored XSS that executes in the frontend.","url":"https://insights.sbomify.com/CVE-2022-2171/"}