{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-3861 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-3861 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3861 is a high-severity unsafe deserialization vulnerability in MuffinGroup Betheme, published on 21 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3861 and fix it if it is affected.\n\nWhat it is: CVE-2022-3861 is a high-severity unsafe deserialization vulnerability in MuffinGroup Betheme, published on 21 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-3861 in the wild and no public exploit code.\n\nAffected product: MuffinGroup Betheme. 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-2022-3861/ (Markdown: https://insights.sbomify.com/CVE-2022-3861/index.md)","id":"CVE-2022-3861","markdown":"https://insights.sbomify.com/CVE-2022-3861/index.md","name":"CVE-2022-3861","record":{"aliases":["GHSA-qmhr-xwh2-cg99"],"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 theme","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit PHP object injection in the Betheme WordPress theme to execute code or access data via unsafe deserialization.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"betheme","vendor":"muffingroup"}],"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-502","name":"Deserialization of Untrusted Data"}],"description":"The Betheme theme for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 26.5.1.4 via deserialization of untrusted input supplied via the import, mfn-items-import-page, and mfn-items-import parameters passed through the mfn_builder_import, mfn_builder_import_page, importdata, importsinglepage, and importfromclipboard functions.  This makes it possible for authenticated attackers, with subscriber level permissions and above to inject a PHP Object. The additional presence of a POP chain would make it possible for attackers to execute code, retrieve sensitive data, delete files, etc..","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":"Betheme \u003c= 26.5.1.4 - Authenticated (Subscriber+) PHP Object Injection","id":"CVE-2022-3861","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Livemesh Addons for Elementor \u003c 7.2.4 - Admin+ Stored XSS","id":"CVE-2022-3862"},"packages":[],"prev":{"headline":"Visual Email Designer for WooCommerce \u003c 1.7.2 - Multiple Author+ SQLi","id":"CVE-2022-3860"},"products":["Betheme"],"published":"2022-11-21","related":[{"cvss_score":8.8,"headline":"Betheme \u003c= 27.5.6 - Authenticated (Contributor+) PHP Object Injection","id":"CVE-2024-2694","kev_date_added":null,"published":"2024-08-30"},{"cvss_score":8.2,"headline":"WordPress BeTheme theme \u003c= 27.1.1 - Author+ Broken Access Control vulnerability","id":"CVE-2023-39998","kev_date_added":null,"published":"2024-06-19"},{"cvss_score":7.6,"headline":"WordPress BeTheme theme \u003c= 27.1.1 - Contributor+ Broken Access Control vulnerability","id":"CVE-2023-47770","kev_date_added":null,"published":"2024-06-19"},{"cvss_score":7.1,"headline":"WordPress Betheme Theme \u003c= 26.7.5 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-29101","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":6.4,"headline":"Betheme \u003c= 28.0.3 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2025-3077","kev_date_added":null,"published":"2025-04-16"},{"cvss_score":6.4,"headline":"Betheme \u003c= 27.6.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom JS","id":"CVE-2025-0450","kev_date_added":null,"published":"2025-01-21"}],"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":["MuffinGroup"]},"summary":"Authenticated attackers can exploit PHP object injection in the Betheme WordPress theme to execute code or access data via unsafe deserialization.","url":"https://insights.sbomify.com/CVE-2022-3861/"}