Vigilant <= 2.10.2 - Unauthenticated Stored Cross-Site Scripting

7.2
Improper Neutralization of Input During Web Page Generation
CVE CVE-2026-81754
CVSS 7.2 (High)
Publicly Published September 10, 2026
Last Updated September 11, 2026
Researcher Sebastian Albrecht (mySebbe)

Description

The Vigilant – 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner… plugin for WordPress is vulnerable to Stored Cross-Site Scripting via User-Agent Header in all versions up to, and including, 2.10.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 malicious payload is delivered passively by any unauthenticated visitor who triggers a failed login attempt with a crafted User-Agent header, requiring no further interaction from the attacker once stored.

Learn more about Cross-Site Scripting vulnerabilities and how to prevent them.

References

Share

Vulnerability Details for Vigilant – 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner…

Software Type Plugin
Software Slug vigilante (view on wordpress.org)
Patched? Yes
Remediation Update to version 2.10.3, or a newer patched version
Affected Version
  • <= 2.10.2
Patched Version
  • 2.10.3

Recent vulnerabilities in Vigilant – 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner…

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation