{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-5709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-5709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5709 is a high-severity path traversal vulnerability in WPBakery Page Builder, published on 6 Aug 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-5709 and fix it if it is affected.\n\nWhat it is: CVE-2024-5709 is a high-severity path traversal vulnerability in WPBakery Page Builder, published on 6 Aug 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-5709 in the wild and no public exploit code.\n\nAffected product: WPBakery Page Builder. 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-5709/ (Markdown: https://insights.sbomify.com/CVE-2024-5709/index.md)","id":"CVE-2024-5709","markdown":"https://insights.sbomify.com/CVE-2024-5709/index.md","name":"CVE-2024-5709","record":{"aliases":["GHSA-8wgf-r9xp-xr3r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers with Author access can exploit a Local File Inclusion vulnerability in WPBakery to execute arbitrary PHP code and read sensitive data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"page_builder","vendor":"wpbakery"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The WPBakery Visual Composer plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 7.7 via the 'layout_name' parameter. This makes it possible for authenticated attackers, with Author-level access and above, and with post permissions granted by an Administrator, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.","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":"WPBakery \u003c= 7.7 - Authenticated (Author+) Local File Inclusion","id":"CVE-2024-5709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Access Control in Team Management in berriai/litellm","id":"CVE-2024-5710"},"packages":[],"prev":{"headline":"WPBakery \u003c= 7.7 - Authenticated (Author+) Stored Cross-Site Scripting","id":"CVE-2024-5708"},"products":["WPBakery Page Builder"],"published":"2024-08-06","related":[{"cvss_score":6.5,"headline":"WordPress Classic Addons – WPBakery Page Builder plugin \u003c= 3.5 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-43953","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":6.5,"headline":"WordPress WPBakery Page Builder Plugin \u003c 6.13.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-31213","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":6.4,"headline":"WPBakery Page Builder \u003c= 8.6 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2025-10006","kev_date_added":null,"published":"2025-10-18"},{"cvss_score":6.4,"headline":"WPBakery Page Builder \u003c= 8.6.1 - Stored Cross-Site Scripting via Custom JS Module","id":"CVE-2025-11160","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":6.4,"headline":"WPBakery Page Builder \u003c= 8.6.1 - Stored Cross-Site Scripting via vc_custom_heading Shortcode","id":"CVE-2025-11161","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":6.4,"headline":"WPBakery Page Builder for WordPress \u003c= 8.5 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2025-7502","kev_date_added":null,"published":"2025-08-06"}],"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":["wpbakery"]},"summary":"Authenticated attackers with Author access can exploit a Local File Inclusion vulnerability in WPBakery to execute arbitrary PHP code and read sensitive data.","url":"https://insights.sbomify.com/CVE-2024-5709/"}