{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3360 exists.","fix":"No fix has been published for CVE-2023-3360 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3360 is a low-severity unsafe deserialization vulnerability in Unknown Weaver Show Posts, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-3360 and fix it if it is affected.\n\nWhat it is: CVE-2023-3360 is a low-severity unsafe deserialization vulnerability in Unknown Weaver Show Posts, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3360 exists.\n\nAffected product: Unknown Weaver Show Posts. 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-3360/ (Markdown: https://insights.sbomify.com/CVE-2023-3360/index.md)","id":"CVE-2023-3360","markdown":"https://insights.sbomify.com/CVE-2023-3360/index.md","name":"CVE-2023-3360","record":{"aliases":["GHSA-xw87-h6v2-j87m"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"A high-privilege user importing a malicious file can trigger PHP object injection, potentially leading to code execution on the WordPress site.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The Weaver Show Posts WordPress plugin before 1.8.1 unserialises the content of an imported file, which could lead to PHP object injections issues when a high privilege user import a malicious file and a suitable gadget chain is present on the blog.","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":"Weaver Show Posts \u003c 1.8.1 - Admin+ PHP Object Injection","id":"CVE-2023-3360","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"S3 credentials included when exporting elyra notebook","id":"CVE-2023-3361"},"packages":[],"prev":{"headline":"Null dereference in Kernel","id":"CVE-2023-3359"},"products":["Weaver Show Posts"],"published":"2026-09-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["Unknown"]},"summary":"A high-privilege user importing a malicious file can trigger PHP object injection, potentially leading to code execution on the WordPress site.","url":"https://insights.sbomify.com/CVE-2023-3360/"}