{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-10035 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-10035 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-10035 is a medium-severity unsafe deserialization vulnerability in wpweaver Turnkey bbPress by WeaverTheme, published on 16 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-10035 and fix it if it is affected.\n\nWhat it is: CVE-2026-10035 is a medium-severity unsafe deserialization vulnerability in wpweaver Turnkey bbPress by WeaverTheme, published on 16 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-10035 in the wild and no public exploit code.\n\nAffected product: wpweaver Turnkey bbPress by WeaverTheme. 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-2026-10035/ (Markdown: https://insights.sbomify.com/CVE-2026-10035/index.md)","id":"CVE-2026-10035","markdown":"https://insights.sbomify.com/CVE-2026-10035/index.md","name":"CVE-2026-10035","record":{"aliases":["GHSA-v2rq-f773-w46v"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Administrators can trigger PHP object injection via deserialization of uploaded files, potentially leading to code execution or data exposure if a POP chain exists.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The Turnkey bbPress by WeaverTheme plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.7.1 via deserialization of untrusted input in the wvrbbp_set_to_serialized_values() function (reached through the wvrbbp_save_restore() settings-restore handler). The function reads the raw contents of an administrator-uploaded file and passes them directly to unserialize() without any validation. This makes it possible for authenticated attackers, with administrator-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable plugin itself; however, if a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.","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":"Turnkey bbPress by WeaverTheme \u003c= 1.7.1 - Authenticated (Administrator+) PHP Object Injection","id":"CVE-2026-10035","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"SpeechBrain \u003c 1.1.1 Arbitrary Code Execution via CKPT.yaml Parsing","id":"CVE-2026-10036"},"packages":[],"prev":{"headline":"Missing authorization in WP DSGVO Tools (GDPR)","id":"CVE-2026-10034"},"products":["Turnkey bbPress by WeaverTheme"],"published":"2026-08-16","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-17","vendors":["wpweaver"]},"summary":"Administrators can trigger PHP object injection via deserialization of uploaded files, potentially leading to code execution or data exposure if a POP chain exists.","url":"https://insights.sbomify.com/CVE-2026-10035/"}