Skip to main content
VulnerabilityPublished

CVE-2026-97397: Remove Google Fonts (WordPress plugin) · Cross-site Scripting

Affects Remove Google Fonts (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 4 Nov 2026, 11:45 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
easywpstuffRemove Google Fonts – Disable, Block, or Replace with Bunny Fonts for GDPR ComplianceAffected
  • <=1.7
Fixed in–

AI-suggested

Users should consider disabling the plugin's Remove mode or the plugin entirely until a fix is available. Additionally, manual review and moderation of comments should be enforced to prevent publishing malicious content. Monitor the vendor's advisory channels for updates regarding a patch or official remediation.

Description

The Remove Google Fonts – Disable, Block, or Replace with Bunny Fonts for GDPR Compliance WordPress plugin up to version 1.7 is vulnerable to stored cross-site scripting (XSS) via the comment field. This vulnerability arises from insufficient input sanitization and output escaping in the plugin's Remove mode, allowing unauthenticated attackers to inject malicious scripts that execute when users view the affected pages. Exploitation requires the malicious comment to be published either automatically for known commenters or through manual approval by a moderator.

References

Community reviews

Loading reviews…