{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-2435 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-2435 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-2435 is a high-severity path traversal vulnerability in timhodson Blog-in-Blog, published on 31 May 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-2435 and fix it if it is affected.\n\nWhat it is: CVE-2023-2435 is a high-severity path traversal vulnerability in timhodson Blog-in-Blog, published on 31 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-2435 in the wild and no public exploit code.\n\nAffected product: timhodson Blog-in-Blog. 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-2023-2435/ (Markdown: https://insights.sbomify.com/CVE-2023-2435/index.md)","id":"CVE-2023-2435","markdown":"https://insights.sbomify.com/CVE-2023-2435/index.md","name":"CVE-2023-2435","record":{"aliases":["GHSA-22pm-3j5r-cgw3"],"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":"high_privilege","summary":"Authenticated editors can exploit a shortcode vulnerability to include arbitrary files, leading to code execution or data disclosure.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"blog-in-blog","vendor":"blog-in-blog_project"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 Blog-in-Blog plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.0.0 via a shortcode attribute. This allows editor-level, and above, attackers 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":"Blog-in-Blog \u003c= 2.0.0 - Authenticated (Editor+) Local File Inclusion via Shortcode","id":"CVE-2023-2435","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Blog-in-Blog \u003c= 2.0.0 - Authenticated (Editor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2023-2436"},"packages":[],"prev":{"headline":"Nested Pages \u003c= 3.2.3 - Missing Authorization to Authenticated (Editor+) Plugin Settings Reset","id":"CVE-2023-2434"},"products":["Blog-in-Blog"],"published":"2023-05-31","related":[{"cvss_score":4.4,"headline":"Blog-in-Blog \u003c= 2.0.0 - Authenticated (Editor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2023-2436","kev_date_added":null,"published":"2023-05-31"}],"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":["timhodson"]},"summary":"Authenticated editors can exploit a shortcode vulnerability to include arbitrary files, leading to code execution or data disclosure.","url":"https://insights.sbomify.com/CVE-2023-2435/"}