{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4168 exists.","fix":"No fix has been published for CVE-2009-4168 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-4168 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Dec 2009. 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-2009-4168 and fix it if it is affected.\n\nWhat it is: CVE-2009-4168 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Dec 2009. 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-2009-4168 exists.\n\nAffected product: n/a. 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-2009-4168/ (Markdown: https://insights.sbomify.com/CVE-2009-4168/index.md)","id":"CVE-2009-4168","markdown":"https://insights.sbomify.com/CVE-2009-4168/index.md","name":"CVE-2009-4168","record":{"aliases":["GHSA-f865-32w6-7639"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Remote attackers can inject arbitrary web script or HTML via the tagcloud parameter in the WP-Cumulus plugin, affecting WordPress and Joomla users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wp-cumulus","vendor":"roytanck"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Cross-site scripting (XSS) vulnerability in Roy Tanck tagcloud.swf, as used in the WP-Cumulus plugin before 1.23 for WordPress and the Joomulus module 2.0 and earlier for Joomla!, allows remote attackers to inject arbitrary web script or HTML via the tagcloud parameter in a tags action. Cross-site scripting (XSS) vulnerability in tagcloud.swf in the WP-Cumulus Plug-in before 1.23 for WordPress allows remote attackers to inject arbitrary web script or HTML via the tagcloud parameter.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-11-09","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-11-09","kind":"exploitdb","ref":"33371","stars":null,"title":"WordPress Plugin WP-Cumulus 1.x - 'tagcloud.swf' Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2009-4168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2009"},"n_packages":0,"n_references":16,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2009-4169"},"packages":[],"prev":{"headline":"Unspecified vulnerability in the Automatic Base Tags for RealUrl (lt_basetag) extension 1.0.0 for TYPO3 allows remote attackers to conduct \"","id":"CVE-2009-4167"},"products":["n/a"],"published":"2009-12-02","related":[{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2009-4170","kev_date_added":null,"published":"2009-12-02"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2009-4169","kev_date_added":null,"published":"2009-12-02"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary web script or HTML via the tagcloud parameter in the WP-Cumulus plugin, affecting WordPress and Joomla users.","url":"https://insights.sbomify.com/CVE-2009-4168/"}