CVE-2026-89417: OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy. (WordPress plugin) · Cross-site Scripting
Affects OMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy. (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| daanvandenberghOMGF | GDPR/DSGVO Compliant, Faster Google Fonts. Easy. | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, administrators should consider configuring their web servers to serve .tmp files with appropriate Content-Type headers and enable X-Content-Type-Options to prevent MIME sniffing. Additionally, monitoring for unusual activity related to the comments-atom feed and restricting access to this feed may reduce exposure.
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/cd760ff9-fe72-44d6-a5f0-212a20dd2a51?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/host-webfonts-local/tags/6.3.10/src/Download.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/host-webfonts-local/tags/6.3.10/src/Frontend/Process.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/host-webfonts-local/tags/6.3.10/src/Frontend/Process.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/host-webfonts-local/tags/6.3.10/src/Optimize.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/host-webfonts-local/tags/6.3.10/src/Optimize.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&new=3707539%40host-webfonts-local%2Ftags%2F6.3.11&old=3641590%40host-webfonts-local%2Ftags%2F6.3.10 (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3707539/host-webfonts-local/trunk/src/Frontend/Process.php (opens in a new tab)