Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts Security & Risk Analysis

wordpress.org/plugins/yabe-webfont

Easy self-host Google Fonts, Adobe Fonts support, or upload custom fonts in WordPress. Integrated into the most popular themes and page builders.

5K active installs v1.0.98 PHP 7.4+ WP 6.0+ Updated Feb 5, 2026
adobe-fontscustom-fontsdsgvogdprgoogle-fonts
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts Safe to Use in 2026?

Generally Safe

Score 100/100

Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1mo ago
Risk Assessment

The "yabe-webfont" plugin version 1.0.98 exhibits a generally positive security posture based on the provided static analysis. The plugin has no known vulnerabilities (CVEs), no recorded common vulnerability types, and a clean history, which suggests a history of secure development practices. The attack surface is remarkably small, with zero identified entry points, indicating that there are no direct ways to interact with the plugin's functionality in a way that could be exploited through common vectors like AJAX, REST API, or shortcodes. Furthermore, the absence of file operations and external HTTP requests reduces potential risks associated with file manipulation or remote code execution. However, the analysis does highlight a critical concern regarding output escaping, with 100% of identified outputs not being properly escaped. This lack of escaping is a significant weakness that could lead to cross-site scripting (XSS) vulnerabilities if any user-supplied data is ever rendered directly in the output, even with the current lack of direct entry points.

Key Concerns

  • Output not properly escaped
Vulnerabilities
None known

Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts Code Analysis

Dangerous Functions
0
Raw SQL Queries
3
28 prepared
Unescaped Output
4
0 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

SQL Query Safety

90% prepared31 total queries

Output Escaping

0% escaped4 total outputs
Attack Surface

Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts Attack Surface

Entry Points0
Unprotected0
Maintenance & Trust

Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 5, 2026
PHP min version7.4
Downloads26K

Community Trust

Rating100/100
Number of ratings25
Active installs5K
Developer Profile

Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts Developer Profile

Sua

3 plugins · 8K total installs

94
trust score
Avg Security Score
100/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/yabe-webfont/src/Builder/Gutenberg/build/index.js/wp-content/plugins/yabe-webfont/src/Builder/Gutenberg/build/style-index.css/wp-content/plugins/yabe-webfont/src/Builder/Gutenberg/build/view.js

HTML / DOM Fingerprints

CSS Classes
yabe-webfont-block
JS Globals
yabeWebfontBuilderiusFontsbuilderiusBackend
FAQ

Frequently Asked Questions about Yabe Webfont – Use Custom Fonts, Google Fonts or Adobe Fonts