{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-5503 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-5503 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5503 is a high-severity path traversal vulnerability in codevibrant WP Blog Post Layouts, published on 21 Jun 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-5503 and fix it if it is affected.\n\nWhat it is: CVE-2024-5503 is a high-severity path traversal vulnerability in codevibrant WP Blog Post Layouts, published on 21 Jun 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-5503 in the wild and no public exploit code.\n\nAffected product: codevibrant WP Blog Post Layouts. 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-5503/ (Markdown: https://insights.sbomify.com/CVE-2024-5503/index.md)","id":"CVE-2024-5503","markdown":"https://insights.sbomify.com/CVE-2024-5503/index.md","name":"CVE-2024-5503","record":{"aliases":["GHSA-rpr4-fpwh-9vfr"],"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 a local file inclusion vulnerability in the WP Blog Post Layouts plugin to execute arbitrary PHP code on the server.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_blog_post_layouts","vendor":"codevibrant"}],"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 WP Blog Post Layouts plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1.3. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary PHP 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":"WP Blog Post Layouts \u003c= 1.1.3 - Authenticated (Contributor+) Local File Inlcusion","id":"CVE-2024-5503","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":0,"n_references":8,"next":{"headline":"Cross-site scripting in Rife Extensions \u0026 Templates for Elementor","id":"CVE-2024-5504"},"packages":[],"prev":{"headline":"Piotnet Addons For Elementor \u003c= 2.4.30 - Authenticated (Contributor+) Stored Cross-Site Scripting via Multiple Widgets","id":"CVE-2024-5502"},"products":["WP Blog Post Layouts"],"published":"2024-06-21","related":[],"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":["codevibrant"]},"summary":"Authenticated contributors can exploit a local file inclusion vulnerability in the WP Blog Post Layouts plugin to execute arbitrary PHP code on the server.","url":"https://insights.sbomify.com/CVE-2024-5503/"}