{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3615 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3615 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3615 is a medium-severity cross-site scripting vulnerability in maxfoundry Media Library Folders, published on 19 Apr 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-2024-3615 and fix it if it is affected.\n\nWhat it is: CVE-2024-3615 is a medium-severity cross-site scripting vulnerability in maxfoundry Media Library Folders, published on 19 Apr 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: There is no known exploitation of CVE-2024-3615 in the wild and no public exploit code.\n\nAffected product: maxfoundry Media Library Folders. 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-2024-3615/ (Markdown: https://insights.sbomify.com/CVE-2024-3615/index.md)","id":"CVE-2024-3615","markdown":"https://insights.sbomify.com/CVE-2024-3615/index.md","name":"CVE-2024-3615","record":{"aliases":["GHSA-v4qv-r5g6-wxrp"],"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":"Unauthenticated attackers can inject arbitrary web scripts via the 's' parameter, executing code in victim browsers if they click a crafted link.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"media_library_folders","vendor":"maxfoundry"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","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-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Media Library Folders plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 8.2.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.","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":"Media Library Folders \u003c= 8.2.0 - Reflected Cross-Site Scripting via 's'","id":"CVE-2024-3615","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"SourceCodester Warehouse Management System pengguna.php cross site scripting","id":"CVE-2024-3616"},"packages":[],"prev":{"headline":"SourceCodester Warehouse Management System customer.php cross site scripting","id":"CVE-2024-3614"},"products":["Media Library Folders"],"published":"2024-04-19","related":[{"cvss_score":8.5,"headline":"WordPress Media Library Folders plugin \u003c= 8.1.7 - Auth. SQL Injection vulnerability","id":"CVE-2024-30486","kev_date_added":null,"published":"2024-03-29"},{"cvss_score":6.5,"headline":"Media Library Folders \u003c= 8.2.2 - Authenticated (Subscriber+) Second-Order SQL Injection","id":"CVE-2024-7857","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":6.5,"headline":"WordPress Media Library Folders plugin \u003c= 8.1.8 - Directory Traversal vulnerability","id":"CVE-2024-31287","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":6.3,"headline":"Media Library Folders \u003c= 8.2.3 - Missing Authorization on Various Functions","id":"CVE-2024-7858","kev_date_added":null,"published":"2024-08-30"},{"cvss_score":5.4,"headline":"WordPress Media Library Folders plugin \u003c= 7.1.1 - Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2022-41634","kev_date_added":null,"published":"2022-11-18"},{"cvss_score":4.3,"headline":"Media Library Folders \u003c= 8.3.0 - Missing Authorization to Plugin Settings Change","id":"CVE-2025-0935","kev_date_added":null,"published":"2025-02-15"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["maxfoundry"]},"summary":"Unauthenticated attackers can inject arbitrary web scripts via the 's' parameter, executing code in victim browsers if they click a crafted link.","url":"https://insights.sbomify.com/CVE-2024-3615/"}