CVE-2026-119178 · Other
NO FIX YET · SEE WHAT TO DO
The Smart Cookie Kit WordPress plugin up to and including 2.3.2 fails to sanitize the 'comment' parameter, so attacker-supplied HTML survives saving and runs as script when a page is rendered. An attacker can run JavaScript in the browser of visitors to the affected public post, such as an administrator.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Smart Cookie Kit WordPress plugin version 2.3.2 or earlier are exposed. Exploitation requires an administrator to approve the malicious comment and then view the affected public post, so sites without this plugin can skip it.
Not affected if plugin-not-installed, plugin-updated
Who cares smart-cookie-kit, wordpress
2.3.2 or earlier2.3.2; the fixed version is not stated in the sourcesThe Smart Cookie Kit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.3.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is specifically crafted to survive wp_kses on save by storing hostile characters inside allowed HTML elements, with the attribute-breaking double-quote smuggled inside a permitted <code> body and reconstructed into a <abbr title> attribute only at render time by the plugin's own output buffer; exploitation requires an administrator to approve the comment and subsequently view the affected public post.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.