CVE-2026-9016

{"id": "CVE-2026-9016", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-9016", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-06T11:33:44.814740Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security@wordfence.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security@wordfence.com", "affectedData": [{"vendor": "qriouslad", "product": "Debug Log Manager \u2013 Conveniently Monitor and Inspect Errors", "versions": [{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "2.5.0"}], "defaultStatus": "unaffected"}]}], "published": "2026-06-06T05:16:29.657", "references": [{"url": "https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/bootstrap.php#L123", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/bootstrap.php#L556", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/classes/class-debug-log.php#L1947", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/debug-log-manager/tags/2.4.3/classes/class-debug-log.php#L1961", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3543321%40debug-log-manager&new=3543321%40debug-log-manager&sfp_email=&sfph_mail=", "source": "security@wordfence.com"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/25abca87-1be2-427e-ab01-377d52917052?source=cve", "source": "security@wordfence.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@wordfence.com", "description": [{"lang": "en", "value": "CWE-117"}]}], "descriptions": [{"lang": "en", "value": "The Debug Log Manager \u2013 Conveniently Monitor and Inspect Errors plugin for WordPress is vulnerable to Improper Output Neutralization for Logs in all versions up to, and including, 2.5.0. This is due to the `log_js_errors()` AJAX handler being registered for unauthenticated users via `wp_ajax_nopriv_log_js_errors` and gated only by a nonce that is publicly disclosed in every front-end page's HTML through `wp_localize_script()` whenever JavaScript error logging is enabled, providing no real authorization barrier. This makes it possible for unauthenticated attackers to inject arbitrary forged entries into the site's WordPress debug log by supplying attacker-controlled values for the `message`, `script`, `lineNo`, `columnNo`, and `pageUrl` fields \u2014 enabling spoofing of error and incident records, obscuring malicious activity within fabricated log noise, and misleading administrators who rely on the log for triage. This vulnerability is only exploitable when the plugin's JavaScript error logging feature is enabled, as the requisite nonce is only published into the page HTML under that condition."}, {"lang": "es", "value": "El plugin Debug Log Manager - Conveniently Monitor and Inspect Errors para WordPress es vulnerable a la Neutralizaci\u00f3n Inadecuada de Salida para Registros en todas las versiones hasta la 2.5.0, inclusive. Esto se debe a que el gestor AJAX 'log_js_errors()' est\u00e1 registrado para usuarios no autenticados a trav\u00e9s de 'wp_ajax_nopriv_log_js_errors' y est\u00e1 protegido \u00fanicamente por un nonce que se divulga p\u00fablicamente en el HTML de cada p\u00e1gina de front-end a trav\u00e9s de 'wp_localize_script()' siempre que el registro de errores de JavaScript est\u00e9 habilitado, lo que no proporciona una barrera de autorizaci\u00f3n real. Esto hace posible que atacantes no autenticados inyecten entradas falsificadas arbitrarias en el registro de depuraci\u00f3n de WordPress del sitio al proporcionar valores controlados por el atacante para los campos 'message', 'script', 'lineNo', 'columnNo' y 'pageUrl', lo que permite la suplantaci\u00f3n de registros de errores y de incidentes, ocultando actividad maliciosa dentro de ruido de registro fabricado y enga\u00f1ando a los administradores que conf\u00edan en el registro para la clasificaci\u00f3n. Esta vulnerabilidad solo es explotable cuando la funci\u00f3n de registro de errores de JavaScript del plugin est\u00e1 habilitada, ya que el nonce requerido solo se publica en el HTML de la p\u00e1gina bajo esa condici\u00f3n."}], "lastModified": "2026-07-23T07:10:00.113", "sourceIdentifier": "security@wordfence.com"}