{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-4330 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-4330 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4330 is a medium-severity cross-site scripting vulnerability in Unknown WP Attachments, published on 16 Jan 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-4330 and fix it if it is affected.\n\nWhat it is: CVE-2022-4330 is a medium-severity cross-site scripting vulnerability in Unknown WP Attachments, published on 16 Jan 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-4330 in the wild and no public exploit code.\n\nAffected product: Unknown WP Attachments. 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-4330/ (Markdown: https://insights.sbomify.com/CVE-2022-4330/index.md)","id":"CVE-2022-4330","markdown":"https://insights.sbomify.com/CVE-2022-4330/index.md","name":"CVE-2022-4330","record":{"aliases":["GHSA-7cjc-c9jv-7878"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Admins can inject malicious scripts via unsanitized settings in WP Attachments, bypassing unfiltered_html restrictions in multisite setups.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_attachments","vendor":"marcomilesi"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 WP Attachments WordPress plugin before 5.0.6 does not sanitise and escape some of its settings, which could allow high privilege users such as admin 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":"none_known"},"has_fix":null,"headline":"WP Attachments \u003c 5.0.6 - Admin+ Stored XSS","id":"CVE-2022-4330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in GitLab","id":"CVE-2022-4331"},"packages":[],"prev":{"headline":"Product list Widget for Woocommerce \u003c= 1.0 - Reflected XSS","id":"CVE-2022-4329"},"products":["WP Attachments"],"published":"2023-01-16","related":[{"cvss_score":4.8,"headline":"WP Attachments \u003c 5.0.5 - Admin+ Stored Cross-Site Scripting","id":"CVE-2022-3469","kev_date_added":null,"published":"2022-11-14"},{"cvss_score":4.3,"headline":"WordPress WP Attachments Plugin \u003c= 5.0.11 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-45651","kev_date_added":null,"published":"2023-10-16"}],"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":"Admins can inject malicious scripts via unsanitized settings in WP Attachments, bypassing unfiltered_html restrictions in multisite setups.","url":"https://insights.sbomify.com/CVE-2022-4330/"}