{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-24961 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24961 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24961 is a medium-severity cross-site scripting vulnerability in Unknown WordPress File Upload, published on 7 Mar 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-2021-24961 and fix it if it is affected.\n\nWhat it is: CVE-2021-24961 is a medium-severity cross-site scripting vulnerability in Unknown WordPress File Upload, published on 7 Mar 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-2021-24961 in the wild and no public exploit code.\n\nAffected product: Unknown WordPress File Upload. 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-2021-24961/ (Markdown: https://insights.sbomify.com/CVE-2021-24961/index.md)","id":"CVE-2021-24961","markdown":"https://insights.sbomify.com/CVE-2021-24961/index.md","name":"CVE-2021-24961","record":{"aliases":["GHSA-v8xx-gxhg-qqpr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress File Upload plugin","requires_auth":"low_privilege","summary":"Contributors can inject malicious scripts via unescaped shortcode arguments in the WordPress File Upload plugin, leading to stored XSS.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wordpress_file_upload","vendor":"iptanus"},{"product":"wordpress_file_upload_pro","vendor":"iptanus"}],"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-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WordPress File Upload WordPress plugin before 4.16.3, wordpress-file-upload-pro WordPress plugin before 4.16.3 does not escape some of its shortcode argument, which could allow users with a role as low as Contributor to perform Cross-Site Scripting attacks","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 File Upload \u003c 4.16.3 - Contributor+ Stored Cross-Site Scripting via Shortcode","id":"CVE-2021-24961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"WordPress File Upload \u003c 4.16.3 - Contributor+ Path Traversal to RCE","id":"CVE-2021-24962"},"packages":[],"prev":{"headline":"WordPress File Upload \u003c 4.16.3 - Contributor+ Stored Cross-Site Scripting via Malicious SVG","id":"CVE-2021-24960"},"products":["WordPress File Upload","wordpress-file-upload-pro"],"published":"2022-03-07","related":[{"cvss_score":9.8,"headline":"Code injection in Iptanus File Upload","id":"CVE-2024-11613","kev_date_added":null,"published":"2025-01-08"},{"cvss_score":9.8,"headline":"WordPress File Upload \u003c= 4.24.12 - Unuathenticated Remote Code Execution","id":"CVE-2024-11635","kev_date_added":null,"published":"2025-01-08"},{"cvss_score":9.8,"headline":"The WordPress File Upload plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 4.24.11 via wfu_file_downloader.php.","id":"CVE-2024-9047","kev_date_added":null,"published":"2024-10-12"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-10564","kev_date_added":null,"published":"2020-03-13"},{"cvss_score":8.8,"headline":"WordPress File Upload \u003c 4.16.3 - Contributor+ Path Traversal to RCE","id":"CVE-2021-24962","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":7.5,"headline":"WordPress File Upload \u003c= 4.24.13 - Unauthenticated Path Traversal to Arbitrary File Read in wfu_file_downloader.php","id":"CVE-2024-9939","kev_date_added":null,"published":"2025-01-08"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2015-9338","kev_date_added":null,"published":"2019-08-22"}],"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":"Contributors can inject malicious scripts via unescaped shortcode arguments in the WordPress File Upload plugin, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2021-24961/"}