CVE-2026-89417
Received Received - Intake

Stored XSS in OMGF | GDPR/DSGVO Compliant Google Fonts Plugin

Publication date: 2026-10-07

Last updated on: 2026-10-07

Assigner: Wordfence

Description
The OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy. plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 's' Search Parameter via comments-atom Feed in all versions up to, and including, 6.3.10 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 that the front-end server serves the retained .tmp file without a Content-Type or X-Content-Type-Options header, enabling MIME-sniffing browsers such as Chromium to execute the injected script — a condition present by default on many Apache and nginx/php-fpm deployments.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-07
Last Modified
2026-10-07
Generated
2026-10-07
AI Q&A
2026-10-07
EPSS Evaluated
N/A
NVD
CVE-2026-89417
EUVD
EUVD-2026-94220

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
daanvandenbergh OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy. 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This WordPress plugin vulnerability allows unauthenticated attackers to inject malicious scripts via the 's' search parameter in comments-atom feeds. The issue stems from insufficient input sanitization and output escaping in versions up to 6.3.10. If the server serves a retained .tmp file without proper Content-Type or X-Content-Type-Options headers, browsers may execute the injected script through MIME-sniffing.

Detection Guidance

Check WordPress sites using the OMGF plugin for comments-atom feed injection via the 's' search parameter. Inspect server logs for unusual .tmp file requests without proper Content-Type headers. Use security plugins like Wordfence to scan for stored XSS in comments or feeds.

Impact Analysis

An attacker could steal user sessions, deface your website, redirect visitors to malicious sites, or perform actions on behalf of users. Since no authentication is required, any visitor to an affected site could trigger the exploit if the conditions are met.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity and confidentiality requirements. For HIPAA, it may expose protected health information to unauthorized parties, risking compliance breaches. Both standards mandate safeguards against such exploits.

Mitigation Strategies

Update the OMGF plugin to the latest version beyond 6.3.10. Disable comments-atom feed if unused. Configure servers to enforce Content-Type headers and X-Content-Type-Options. Monitor for suspicious script injections in feeds or comments.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-89417. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart