CVE-2023-51700
WP-Mobile-BankID-Integration WordPress Database Deserialization: Potential for Object Injection
Severity Score
Exploit Likelihood
Affected Versions
Public Exploits
0Exploited in Wild
-Decision
Descriptions
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.
La integración no oficial de Mobile BankID para WordPress permite a los usuarios emplear Mobile BankID para autenticarse en su sitio de WordPress. Antes de la versión 1.0.1, WP-Mobile-BankID-Integration se ve afectado por una vulnerabilidad clasificada como vulnerabilidad de deserialización de datos no confiables, que afecta específicamente escenarios en los que un atacante puede manipular la base de datos. Si actores no autorizados obtienen acceso a la base de datos, podrían aprovechar esta vulnerabilidad para ejecutar ataques de inyección de objetos. Esto podría dar lugar a la ejecución de código no autorizado, manipulación de datos o filtración de datos dentro del entorno de WordPress. Los usuarios del complemento deben actualizar a la versión 1.0.1 (o posterior), donde la serialización y deserialización de los objetos OrderResponse se cambiaron a una matriz almacenada como JSON. Una posible solución para los usuarios que no pueden actualizar inmediatamente es aplicar controles de acceso más estrictos a la base de datos, garantizando que solo las entidades autorizadas y de confianza puedan modificar los datos. Además, implementar herramientas de monitoreo para detectar actividades inusuales en la base de datos podría ayudar a identificar y mitigar posibles intentos de explotación.
The WP-Mobile-BankID-Integration plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and excluding, 1.0.1 via deserialization of untrusted input through the getAuthResponseFromDB function. This makes it possible for attackers to inject a PHP Object. No known POP chain is present in the vulnerable plugin. 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.
CVSS Scores
SSVC
- Decision:-
Timeline
- 2023-12-21 CVE Reserved
- 2023-12-26 CVE Published
- 2024-08-02 CVE Updated
- 2024-09-29 EPSS Updated
- ---------- Exploited in Wild
- ---------- KEV Due Date
- ---------- First Exploit
CWE
- CWE-502: Deserialization of Untrusted Data
CAPEC
References (2)
| URL | Tag | Source |
|---|
| URL | Date | SRC |
|---|
Affected Vendors, Products, and Versions
| Vendor | Product | Version | Other | Status | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Vendor | Product | Version | Other | Status | <-- --> | Vendor | Product | Version | Other | Status |
| Jamieblomerus Search vendor "Jamieblomerus" | Unofficial Mobile Bankid Integration Search vendor "Jamieblomerus" for product "Unofficial Mobile Bankid Integration" | < 1.0.1 Search vendor "Jamieblomerus" for product "Unofficial Mobile Bankid Integration" and version " < 1.0.1" | wordpress |
Affected
| ||||||