{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3500 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3500 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3500 is a high-severity path traversal vulnerability in wpmet ElementsKit Pro, published on 2 May 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-3500 and fix it if it is affected.\n\nWhat it is: CVE-2024-3500 is a high-severity path traversal vulnerability in wpmet ElementsKit Pro, published on 2 May 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-3500 in the wild and no public exploit code.\n\nAffected product: wpmet ElementsKit Pro. 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-3500/ (Markdown: https://insights.sbomify.com/CVE-2024-3500/index.md)","id":"CVE-2024-3500","markdown":"https://insights.sbomify.com/CVE-2024-3500/index.md","name":"CVE-2024-3500","record":{"aliases":["GHSA-8w77-74pj-w6rc"],"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 contributors can exploit Local File Inclusion in ElementsKit Pro widgets to execute arbitrary PHP code or read sensitive data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"elementskit","vendor":"wpmet"}],"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-98","name":"Improper Control of Filename for Include/Require Statement in PHP Program"}],"description":"The ElementsKit Pro plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.6.0 via the Price Menu, Hotspot, and Advanced Toggle widgets. This makes it possible for authenticated attackers, with contributor-level access and above, 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. CVE-2024-43996 is potentially a duplicate of this issue.","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":"Path traversal in ElementsKit Pro","id":"CVE-2024-3500","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":"Exposure of Sensitive Information in lunary-ai/lunary","id":"CVE-2024-3501"},"packages":[],"prev":{"headline":"ElementsKit Elementor addons \u003c= 3.1.0 - Authenticated (Contributor+) Local File Inclusion via Onepage Scroll Module","id":"CVE-2024-3499"},"products":["ElementsKit Pro"],"published":"2024-05-02","related":[{"cvss_score":8.5,"headline":"ElementsKit PRO \u003c= 3.6.1 - Authenticated (Contributor+) Server-Side Request Forgery","id":"CVE-2024-4404","kev_date_added":null,"published":"2024-06-14"},{"cvss_score":6.5,"headline":"WordPress ElementsKit Pro plugin \u003c= 3.6.0 - Local File Inclusion vulnerability","id":"CVE-2024-43996","kev_date_added":null,"published":"2024-09-23"},{"cvss_score":6.4,"headline":"ElementsKit Pro \u003c= 3.7.8 - Authenticated (Contributor+) DOM-Based Stored Cross-Site Scripting via url Parameter","id":"CVE-2025-0321","kev_date_added":null,"published":"2025-01-28"},{"cvss_score":6.4,"headline":"ElementsKit Pro \u003c= 3.6.5 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-7064","kev_date_added":null,"published":"2024-08-15"},{"cvss_score":6.4,"headline":"Cross-site scripting in ElementsKit Pro","id":"CVE-2024-5263","kev_date_added":null,"published":"2024-06-15"},{"cvss_score":6.4,"headline":"ElementsKit Pro \u003c= 3.6.1 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-4452","kev_date_added":null,"published":"2024-05-21"}],"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":["wpmet"]},"summary":"Authenticated contributors can exploit Local File Inclusion in ElementsKit Pro widgets to execute arbitrary PHP code or read sensitive data.","url":"https://insights.sbomify.com/CVE-2024-3500/"}