{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-13494 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-13494 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-13494 is a medium-severity vulnerability in nickboss Iptanus File Upload, published on 25 Feb 2025. 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-13494 and fix it if it is affected.\n\nWhat it is: CVE-2024-13494 is a medium-severity vulnerability in nickboss Iptanus File Upload, published on 25 Feb 2025. 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-13494 in the wild and no public exploit code.\n\nAffected product: nickboss Iptanus 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-2024-13494/ (Markdown: https://insights.sbomify.com/CVE-2024-13494/index.md)","id":"CVE-2024-13494","markdown":"https://insights.sbomify.com/CVE-2024-13494/index.md","name":"CVE-2024-13494","record":{"aliases":["GHSA-97h7-wwch-qv36"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into modifying uploaded file details via CSRF in the WordPress File Upload plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wordpress_file_upload","vendor":"iptanus"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WordPress File Upload plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.25.2. This is due to missing or incorrect nonce validation on the 'wfu_file_details' function. This makes it possible for unauthenticated attackers to modify user data details associated with uploaded files via a forged request granted they can trick a site administrator 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":"WordPress File Upload \u003c= 4.25.2 - Cross-Site Request Forgery in wfu_file_details","id":"CVE-2024-13494","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"GamiPress \u003c= 7.2.1 - Unauthenticated Arbitrary Shortcode Execution via gamipress_ajax_get_logs Function","id":"CVE-2024-13495"},"packages":[],"prev":{"headline":"Sensly Online Presence \u003c= 0.6 - Admin+ Stored XSS","id":"CVE-2024-13493"},"products":["Iptanus File Upload"],"published":"2025-02-25","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["nickboss"]},"summary":"Unauthenticated attackers can trick administrators into modifying uploaded file details via CSRF in the WordPress File Upload plugin.","url":"https://insights.sbomify.com/CVE-2024-13494/"}