CVE-2026-96571

7.2High

Published 18 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite

7.2CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
Limited impact
Weakness
CWE-79

What an attacker gets

Unauthenticated attackers can execute arbitrary JavaScript in the browsers of users viewing comments. This requires no authentication and is triggered when a user views a page containing a malicious comment.

Root cause

The plugin fails to sanitize or escape the href attribute of comment anchors before rendering them.

Affected versions

FancyBox for WordPress plugin up to and including version 3.4.2.

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Fix & remediation

Deactivate and uninstall the FancyBox for WordPress plugin immediately until a patched version is released. There is no configuration-based mitigation for this vulnerability.

remediation — bash
$ wp plugin deactivate fancybox-for-wordpress && wp plugin uninstall fancybox-for-wordpress

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

The FancyBox for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Anchor 'href' Attribute in all versions up to, and including, 3.4.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. Exploitation requires the attacker to wrap the payload anchor around a smilie shortcode (e.g., :mrgreen:), which WordPress renders as an <img> element, satisfying the plugin's a:has(img) enrollment selector and disguising the malicious link as an ordinary comment emoticon.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-96571