{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-10011 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-10011 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10011 is a high-severity path traversal vulnerability in BuddyPress, published on 25 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-10011 and fix it if it is affected.\n\nWhat it is: CVE-2024-10011 is a high-severity path traversal vulnerability in BuddyPress, published on 25 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-10011 in the wild and no public exploit code.\n\nAffected product: BuddyPress. 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-10011/ (Markdown: https://insights.sbomify.com/CVE-2024-10011/index.md)","id":"CVE-2024-10011","markdown":"https://insights.sbomify.com/CVE-2024-10011/index.md","name":"CVE-2024-10011","record":{"aliases":["GHSA-x369-v24j-6g8p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can traverse directories to read or modify files outside the web root, potentially enabling file uploads.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"buddypress","vendor":"buddypress"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The BuddyPress plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 14.1.0 via the id parameter. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform actions on files outside of the originally intended directory and enables file uploads to directories outside of the web root. Depending on server configuration it may be possible to upload files with double extensions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"BuddyPress \u003c= 14.1.0 - Authenticated (Subscriber+) Directory Traversal","id":"CVE-2024-10011","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"Progress UI for WPF format provider unsafe deserialization vulnerability","id":"CVE-2024-10012"},"packages":[],"prev":{"headline":"LearnPress \u003c 4.2.7.2 - Admin+ Stored XSS","id":"CVE-2024-10010"},"products":["BuddyPress"],"published":"2024-10-25","related":[{"cvss_score":8.1,"headline":"BuddyPress privilege escalation via REST API","id":"CVE-2021-21389","kev_date_added":null,"published":"2021-03-26"},{"cvss_score":8,"headline":"Private data exposure via REST API in BuddyPress","id":"CVE-2020-5244","kev_date_added":null,"published":"2020-02-24"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2012-2109","kev_date_added":null,"published":"2012-09-04"},{"cvss_score":7.1,"headline":"WordPress Mass Messaging in BuddyPress Plugin \u003c= 2.2.1 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2025-23798","kev_date_added":null,"published":"2025-01-22"},{"cvss_score":6.5,"headline":"WordPress BuddyPress Plugin \u003c= 11.3.1 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-50880","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2014-1889","kev_date_added":null,"published":"2018-04-10"}],"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":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["buddypress"]},"summary":"Authenticated attackers can traverse directories to read or modify files outside the web root, potentially enabling file uploads.","url":"https://insights.sbomify.com/CVE-2024-10011/"}