# CVE-2026-97397: Remove Google Fonts <= 1.7 - Unauthenticated Stored Cross-Site Scripting via Comment Field via Regex-Mangled Output Buffer

Status: published. Published: 2026-11-04. Updated: 2026-11-04.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- easywpstuff / Remove Google Fonts – Disable, Block, or Replace with Bunny Fonts for GDPR Compliance: ≥ 0; ≤ 1.7 (affected, semver). Source: CNA: Wordfence

## Severity and prioritization

- CVSS 3.1: 7.2 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N; source: CNA: Wordfence

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-79

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/79ff2a5d-ee75-4dc2-85a0-6eb1a032678c?source=cve (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/use-bunnyfont-host-google-fonts/tags/1.7/bunnyfont.php#L253 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/use-bunnyfont-host-google-fonts/tags/1.7/bunnyfont.php#L162 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/use-bunnyfont-host-google-fonts/tags/1.7/bunnyfont.php#L248 (CNA: Wordfence)

## Provenance

- CNA: Wordfence: https://www.cve.org/CVERecord?id=CVE-2026-97397; retrieved 2026-11-04; source updated 2026-11-04

Revision: 0c843a58c9f8f1f3175a1954b55e0bf4920e4ada95046c8ac688b7e76339d295

Canonical: https://y2.dev/cve/CVE-2026-97397

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.