{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2446 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2446 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2446 is a high-severity unsafe deserialization vulnerability in benjaminprojas WP Editor, published on 13 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-2446 and fix it if it is affected.\n\nWhat it is: CVE-2022-2446 is a high-severity unsafe deserialization vulnerability in benjaminprojas WP Editor, published on 13 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-2446 in the wild and no public exploit code.\n\nAffected product: benjaminprojas WP Editor. 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-2446/ (Markdown: https://insights.sbomify.com/CVE-2022-2446/index.md)","id":"CVE-2022-2446","markdown":"https://insights.sbomify.com/CVE-2022-2446/index.md","name":"CVE-2022-2446","record":{"aliases":["GHSA-gm45-ppxv-rfjp"],"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":"Authenticated administrators can achieve arbitrary code execution via PHAR deserialization in the WP Editor plugin.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_editor","vendor":"benjaminrojas"}],"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-502","name":"Deserialization of Untrusted Data"}],"description":"The WP Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'current_theme_root' parameter in versions up to, and including 1.2.9. This makes it possible for authenticated attackers with administrative privileges to call files using a PHAR wrapper that will deserialize and call arbitrary PHP Objects that can be used to perform a variety of malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload.","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":"WP Editor \u003c= 1.2.9 - Authenticated (Admin+) PHAR Deserialization","id":"CVE-2022-2446","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in openstack-keystone","id":"CVE-2022-2447"},"packages":[],"prev":{"headline":"Incorrectly assigned CVE.","id":"CVE-2022-2445"},"products":["WP Editor"],"published":"2024-09-13","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2016-10886","kev_date_added":null,"published":"2019-08-14"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2016-10885","kev_date_added":null,"published":"2019-08-14"},{"cvss_score":7.2,"headline":"WP Editor \u003c= 1.2.9.1 - Authenticated (Administrator+) Directory Traversal to Arbitrary File Update","id":"CVE-2025-3294","kev_date_added":null,"published":"2025-04-17"},{"cvss_score":7.2,"headline":"WP Editor \u003c 1.2.7 - Authenticated SQL injection","id":"CVE-2021-24151","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":5.3,"headline":"WordPress WP Editor plugin \u003c=1.2.7 - Sensitive Data Exposure vulnerability","id":"CVE-2024-25591","kev_date_added":null,"published":"2024-03-17"},{"cvss_score":4.9,"headline":"WP Editor \u003c= 1.2.9.1 - Authenticated (Administrator+) Directory Traversal to Arbitrary File Read","id":"CVE-2025-3295","kev_date_added":null,"published":"2025-04-17"}],"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":["benjaminprojas"]},"summary":"Authenticated administrators can achieve arbitrary code execution via PHAR deserialization in the WP Editor plugin.","url":"https://insights.sbomify.com/CVE-2022-2446/"}