{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0340 exists.","fix":"No fix has been published for CVE-2023-0340 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-0340 is a high-severity path traversal vulnerability in Unknown Custom Content Shortcode, published on 20 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-0340 and fix it if it is affected.\n\nWhat it is: CVE-2023-0340 is a high-severity path traversal vulnerability in Unknown Custom Content Shortcode, published on 20 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0340 exists.\n\nAffected product: Unknown Custom Content Shortcode. 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-0340/ (Markdown: https://insights.sbomify.com/CVE-2023-0340/index.md)","id":"CVE-2023-0340","markdown":"https://insights.sbomify.com/CVE-2023-0340/index.md","name":"CVE-2023-0340","record":{"aliases":["GHSA-q9rp-c9pw-fg3v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can exploit a path traversal vulnerability in the Custom Content Shortcode plugin to read arbitrary files or achieve remote code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"custom_content_shortcode","vendor":"custom_content_shortcode_project"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"The Custom Content Shortcode WordPress plugin through 4.0.2 does not validate one of its shortcode attribute, which could allow users with a contributor role and above to include arbitrary files via a traversal attack. This could also allow them to read non PHP files and retrieve their content. RCE could also be achieved if the attacker manage to upload a malicious image containing PHP code, and then include it via the affected attribute, on a default WP install, authors could easily achieve that given that they have the upload_file capability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Custom Content Shortcode \u003c= 4.0.2 - Contributor+ LFI","id":"CVE-2023-0340","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Stack Buffer Overflow in editorconfig-core-c","id":"CVE-2023-0341"},"packages":[],"prev":{"headline":"AM Web Policy Agent path traversal","id":"CVE-2023-0339"},"products":["Custom Content Shortcode"],"published":"2023-03-20","related":[{"cvss_score":5.4,"headline":"Custom Content Shortcode \u003c= 4.0.2 - Contributor+ Stored XSS","id":"CVE-2023-0273","kev_date_added":null,"published":"2023-03-20"},{"cvss_score":5.4,"headline":"Custom Content Shortcode \u003c 4.0.2 - Authenticated Stored Cross-Site Scripting","id":"CVE-2021-24826","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":4.3,"headline":"Custom Content Shortcode \u003c 4.0.1 - Unauthorised Arbitrary Post Metadata Access","id":"CVE-2021-24824","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":4.3,"headline":"Custom Content Shortcode \u003c 4.0.2 - Authenticated Arbitrary File Access / LFI","id":"CVE-2021-24825","kev_date_added":null,"published":"2022-03-07"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-26","vendors":["Unknown"]},"summary":"Contributors can exploit a path traversal vulnerability in the Custom Content Shortcode plugin to read arbitrary files or achieve remote code execution.","url":"https://insights.sbomify.com/CVE-2023-0340/"}