{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6248 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6248 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6248 is a high-severity path traversal vulnerability in tomdever wpForo Forum, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6248 and fix it if it is affected.\n\nWhat it is: CVE-2026-6248 is a high-severity path traversal vulnerability in tomdever wpForo Forum, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6248 in the wild and no public exploit code.\n\nAffected product: tomdever wpForo Forum. 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-2026-6248/ (Markdown: https://insights.sbomify.com/CVE-2026-6248/index.md)","id":"CVE-2026-6248","markdown":"https://insights.sbomify.com/CVE-2026-6248/index.md","name":"CVE-2026-6248","record":{"aliases":["GHSA-9xxq-3rc5-mg2v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can delete arbitrary files via path traversal in custom profile fields, potentially leading to remote code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The wpForo Forum plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to and including 3.0.5. This is due to two compounding flaws: the Members::update() method does not validate or restrict the value of file-type custom profile fields, allowing authenticated users to store an arbitrary path instead of a legitimate upload path; and the wpforo_fix_upload_dir() sanitization function in ucf_file_delete() only remaps paths that match the expected pattern, and it is passed directly to the unlink() function. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Note: The vulnerability requires a file custom field, which requires the wpForo - User Custom Fields addon plugin.","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":"wpForo Forum \u003c= 3.0.5 - Authenticated (Subscriber+) Arbitrary File Deletion via Custom Profile Field File Path","id":"CVE-2026-6248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Vvveb CMS 1.0.8.2 Remote Code Execution via Media Upload","id":"CVE-2026-6249"},"packages":[],"prev":{"headline":"Cross-site scripting in scratchblocks for WP","id":"CVE-2026-6247"},"products":["wpForo Forum"],"published":"2026-04-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-21","vendors":["tomdever"]},"summary":"Authenticated attackers can delete arbitrary files via path traversal in custom profile fields, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2026-6248/"}