CVE-2026-16149

{"id": "CVE-2026-16149", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-16149", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-24T18:19:02.745662Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security@wordfence.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security@wordfence.com", "affectedData": [{"vendor": "marc4", "product": "Security Hardener", "versions": [{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "2.4.4"}], "defaultStatus": "unaffected"}]}], "published": "2026-08-23T00:16:50.233", "references": [{"url": "https://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L107", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L180", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L204", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L428", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L433", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/security-hardener/tags/2.4.4/security-hardener.php#L439", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/changeset/3630896/security-hardener", "source": "security@wordfence.com"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/64f1a71f-e210-4191-bfb4-56f8568180ed?source=cve", "source": "security@wordfence.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@wordfence.com", "description": [{"lang": "en", "value": "CWE-269"}]}], "descriptions": [{"lang": "en", "value": "The Security Hardener plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 2.4.4. The vulnerability exists because the plugin's user-enumeration protection, which is enabled by default, hooks the rest_endpoints filter via secure_user_endpoints() and overwrites every registered handler's permission_callback on both the /wp/v2/users and /wp/v2/users/(?P<id>[\\d]+) routes \u2014 including POST, PUT, PATCH, and DELETE handlers \u2014 with a bare closure that returns only is_user_logged_in(), completely stripping WordPress Core's original capability checks such as create_users, promote_user, edit_users, and delete_users that WP_REST_Users_Controller normally enforces. This makes it possible for authenticated attackers with Subscriber-level access and above to create new Administrator accounts by sending POST request to /wp/v2/users with administrator role, or to reset an existing Administrator's password by issuing a PUT/POST request to /wp/v2/users/<id>. Because the block_user_enum option defaults to enabled, no special plugin configuration is required \u2014 the overwrite is active on every request as soon as the plugin is installed."}, {"lang": "es", "value": "El plugin Security Hardener para WordPress es vulnerable a una Falta de Autorizaci\u00f3n en todas las versiones hasta la 2.4.4, inclusive. La vulnerabilidad existe porque la protecci\u00f3n de enumeraci\u00f3n de usuarios del plugin, que est\u00e1 habilitada por defecto, engancha el filtro rest_endpoints a trav\u00e9s de secure_user_endpoints() y sobrescribe el permission_callback de cada gestor registrado en ambas rutas /wp/v2/users y /wp/v2/users/(?P<id>[\\d]+) - incluyendo los gestores POST, PUT, PATCH y DELETE - con un cierre simple que solo devuelve is_user_logged_in(), despojando completamente las comprobaciones de capacidad originales del n\u00facleo de WordPress como create_users, promote_user, edit_users y delete_users que WP_REST_Users_Controller normalmente aplica. Esto hace posible que atacantes autenticados con acceso de nivel Suscriptor o superior creen nuevas cuentas de Administrador enviando una solicitud POST a /wp/v2/users con el rol de administrador, o restablezcan la contrase\u00f1a de un Administrador existente emitiendo una solicitud PUT/POST a /wp/v2/users/<id>. Debido a que la opci\u00f3n block_user_enum est\u00e1 habilitada por defecto, no se requiere ninguna configuraci\u00f3n especial del plugin - la sobrescritura est\u00e1 activa en cada solicitud tan pronto como se instala el plugin."}], "lastModified": "2026-10-12T16:10:00.220", "sourceIdentifier": "security@wordfence.com"}