Stored cross-site scripting in Remove Google Fonts WordPress plugin
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
The Remove Google Fonts plugin for WordPress is affected in all versions up to and including 1.7. Insufficient input sanitization and output escaping of the comment field lead to stored cross-site scripting (CWE-79). An unauthenticated attacker can inject a script through a comment that runs when a user accesses an affected page, provided the plugin's Remove mode is active and the comment is published, either automatically for known commenters or after moderator approval.
Written with Claude Haiku 5.5 from the sources below · 2026-11-04
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| easywpstuff | Remove Google Fonts – Disable, Block, or Replace with Bunny Fonts for GDPR Compliance | up to 1.7 | — | No fix listed | CNA |
- Remove Google Fonts – Disable, Block, or Replace with Bunny Fonts for GDPR Compliance Vendoreasywpstuff Affected up to 1.7 Fixed in — No fix listed CNA
Remediation
The sources list no fixed version for Remove Google Fonts (Disable, Block, or Replace with Bunny Fonts for GDPR Compliance).
Written with Claude Haiku 5.5 from the sources below · 2026-11-04
Timeline
- 2026-11-04 Threatist record created from CVE-2026-97397
- 2026-11-04 Alias added: GHSA-h5ch-qpr6-2h3j
- 2026-11-04 CISA SSVC decision points changed
- 2026-11-04 Priority changed: MEDIUM → LOW
References
Other 4
- https://www.wordfence.com/threat-intel/vulnerabilities/id/79ff2a5d-ee75-4dc2-85a0-6eb1a032678c?source=cve
- https://plugins.trac.wordpress.org/browser/use-bunnyfont-host-google-fonts/tags/1.7/bunnyfont.php#L253
- https://plugins.trac.wordpress.org/browser/use-bunnyfont-host-google-fonts/tags/1.7/bunnyfont.php#L162
- https://plugins.trac.wordpress.org/browser/use-bunnyfont-host-google-fonts/tags/1.7/bunnyfont.php#L248
Sources
- CVE-2026-97397 · CVE Program
- CVE-2026-97397 · NVD
- FIRST EPSS
- GHSA-h5ch-qpr6-2h3j · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences