{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2438 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2438 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2438 is a high-severity unsafe deserialization vulnerability in wpmudev Broken Link Checker, published on 6 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-2438 and fix it if it is affected.\n\nWhat it is: CVE-2022-2438 is a high-severity unsafe deserialization vulnerability in wpmudev Broken Link Checker, published on 6 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-2438 in the wild and no public exploit code.\n\nAffected product: wpmudev Broken Link Checker. 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-2438/ (Markdown: https://insights.sbomify.com/CVE-2022-2438/index.md)","id":"CVE-2022-2438","markdown":"https://insights.sbomify.com/CVE-2022-2438/index.md","name":"CVE-2022-2438","record":{"aliases":["GHSA-3pxc-92w9-cmx7"],"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 Broken Link Checker WordPress plugin.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"broken_link_checker","vendor":"managewp"}],"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 Broken Link Checker plugin for WordPress is vulnerable to deserialization of untrusted input via the '$log_file' value in versions up to, and including 1.11.16. This makes it possible for authenticated attackers with administrative privileges and above to call files using a PHAR wrapper that will deserialize the data 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":"Broken Link Checker \u003c= 1.11.16 - Authenticated (Admin+) PHAR Deserialization","id":"CVE-2022-2438","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Deserialization in Easy Digital Downloads – eCommerce Payments and Subscriptions made easy","id":"CVE-2022-2439"},"packages":[],"prev":{"headline":"Feed Them Social – for Twitter feed, Youtube and more \u003c= 2.9.8.5 - Unauthenticated PHAR Deserialization","id":"CVE-2022-2437"},"products":["Broken Link Checker"],"published":"2022-09-06","related":[{"cvss_score":9.3,"headline":"WordPress MainWP Broken Links Checker Extension Plugin \u003c= 4.0 is vulnerable to SQL Injection","id":"CVE-2023-23737","kev_date_added":null,"published":"2023-10-12"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-16521","kev_date_added":null,"published":"2019-10-16"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2019-17207","kev_date_added":null,"published":"2019-10-18"},{"cvss_score":4.8,"headline":"Broken Link Checker \u003c 1.11.20 - Admin+ Cross-Site Scripting","id":"CVE-2022-3922","kev_date_added":null,"published":"2022-12-28"},{"cvss_score":4.7,"headline":"Broken Link Checker \u003c 2.4.2 - Admin+ SSRF","id":"CVE-2024-10903","kev_date_added":null,"published":"2024-12-26"},{"cvss_score":2.4,"headline":"Broken Link Checker Plugin Settings Page core.php options_page cross site scripting","id":"CVE-2014-125105","kev_date_added":null,"published":"2023-06-05"}],"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":["wpmudev"]},"summary":"Authenticated administrators can achieve arbitrary code execution via PHAR deserialization in the Broken Link Checker WordPress plugin.","url":"https://insights.sbomify.com/CVE-2022-2438/"}