{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-51700 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-51700 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51700 is a medium-severity unsafe deserialization vulnerability in jamieblomerus WP-Mobile-BankID-Integration, published on 27 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-51700 and fix it if it is affected.\n\nWhat it is: CVE-2023-51700 is a medium-severity unsafe deserialization vulnerability in jamieblomerus WP-Mobile-BankID-Integration, published on 27 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-51700 in the wild and no public exploit code.\n\nAffected product: jamieblomerus WP-Mobile-BankID-Integration. 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-51700/ (Markdown: https://insights.sbomify.com/CVE-2023-51700/index.md)","id":"CVE-2023-51700","markdown":"https://insights.sbomify.com/CVE-2023-51700/index.md","name":"CVE-2023-51700","record":{"aliases":["GHSA-pqwp-qrp7-grg4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_modify","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"An attacker with database access can exploit unsafe deserialization in the WP-Mobile-BankID-Integration plugin to execute code or manipulate data.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"unofficial_mobile_bankid_integration","vendor":"jamieblomerus"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/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":"Unofficial Mobile BankID Integration for WordPress lets users employ Mobile BankID to authenticate themselves on your WordPress site. Prior to 1.0.1, WP-Mobile-BankID-Integration is affected by a vulnerability classified as a Deserialization of Untrusted Data vulnerability, specifically impacting scenarios where an attacker can manipulate the database. If unauthorized actors gain access to the database, they could exploit this vulnerability to execute object injection attacks. This could lead to unauthorized code execution, data manipulation, or data exfiltration within the WordPress environment.  Users of the plugin should upgrade to version 1.0.1 (or later), where the serialization and deserialization of OrderResponse objects have been switched out to an array stored as JSON.  A possible workaround for users unable to upgrade immediately is to enforce stricter access controls on the database, ensuring that only trusted and authorized entities can modify data. Additionally, implementing monitoring tools to detect unusual database activities could help identify and mitigate potential exploitation attempts.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"WP-Mobile-BankID-Integration WordPress Database Deserialization: Potential for Object Injection","id":"CVE-2023-51700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"@fastify-reply-from JSON Content-Type parsing confusion","id":"CVE-2023-51701"},"packages":[],"prev":{"headline":"OS Command Injection for Fluid Users with JuicefsRuntime","id":"CVE-2023-51699"},"products":["WP-Mobile-BankID-Integration"],"published":"2023-12-27","related":[],"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":"2024-11-27","vendors":["jamieblomerus"]},"summary":"An attacker with database access can exploit unsafe deserialization in the WP-Mobile-BankID-Integration plugin to execute code or manipulate data.","url":"https://insights.sbomify.com/CVE-2023-51700/"}