CVE-2026-97397: Remove Google Fonts <= 1.7 - Unauthenticated Stored Cross-Site Scripting via Comment Field via Regex-Mangled Output Buffer
The Remove Google Fonts – Disable, Block, or Replace with Bunny Fonts for GDPR Compliance plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Field via Regex-Mangled Output Buffer in all versions up to, and including, 1.7 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. Successful exploitation requires the plugin's Remove mode to be active and the malicious comment to be published, either through auto-approval for known commenters or manual moderator approval.
Event History
Frequently Asked Questions
What configuration and workflow conditions are required for exploitation?
The plugin must be operating in Remove mode, and the attacker’s malicious comment must be published. Publication can occur through auto-approval for known commenters or through manual moderator approval.
Can an unauthenticated internet user exploit this issue?
Yes. The vulnerability can be exploited through the comment field without attacker authentication, provided the submitted malicious comment is ultimately published.
Who is exposed to the injected script?
The injected script executes when a user accesses a page containing the published malicious comment. The available data does not limit exposure to a particular user role or browser context.
Which plugin versions are affected?
All versions of Remove Google Fonts up to and including version 1.7 are affected.