Cross-Site Request Forgery (CSRF) vulnerability in Dnesscarkey Use Any Font use-any-font allows Cross Site Request Forgery.This issue affects Use Any Font: from n/a through <= 6.3.08.
Product
wordpress use-any-font vulnerabilities
4 published CVES affecting wordpress use-any-font, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 0
- High
- 1
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress use-any-font CVEs
Newest publication first
-
HighCVSS 8.8 EPSS 0.21%
-
MediumCVSS 6.4
The Use Any Font | Custom Font Uploader plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters such as 'font_key' and 'elements' in versions up to, and including, 6.2.7 due to insufficient input sanitization and output escaping. This makes it pos...
-
MediumCVSS 4.3 EPSS 0.40%
Cross-Site Request Forgery (CSRF) in Use Any Font (WordPress plugin) <= 6.1.7 allows an attacker to deactivate the API key.
-
MediumCVSS 6.1 EPSS 1.5%
The Use Any Font | Custom Font Uploader WordPress plugin before 6.2.1 does not have any authorisation checks when assigning a font, allowing unauthenticated users to sent arbitrary CSS which will then be processed by the frontend for all users. Due to the lack of sanitisation and...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.