Security readout for executives and security teams
Plain-English summary
CVE-2022-27851 affects the WordPress Use Any Font plugin through version 6.1.7. It is a CSRF issue that can let an attacker cause the plugin API key to be deactivated, disrupting font-related plugin functionality rather than exposing data directly.
Executive priority
Treat this as a moderate operational risk for WordPress properties using the affected plugin. It is not described as data theft or remote code execution, but it can disrupt plugin configuration and should be remediated during normal WordPress maintenance cycles.
Technical view
The issue is CWE-352 cross-site request forgery in Use Any Font | Custom Font Uploader <= 6.1.7. CVSS 3.1 is 5.4, with network access, low complexity, no attacker privileges, required user interaction, and limited integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites running the Use Any Font plugin at version 6.1.7 or earlier. Sites not using this plugin, or using a version outside the affected range, are not indicated as affected by the provided sources.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction, consistent with CSRF, and the documented impact is deactivation of the plugin API key.
Researcher notes
The source bundle identifies the affected range and impact but does not include exploit details, fixed version, or confirmed in-the-wild exploitation. Defensive validation should focus on asset inventory, plugin versioning, and checking for unexpected API key deactivation.
Mitigation direction
- Identify WordPress sites using Use Any Font version 6.1.7 or earlier.
- Check the plugin vendor page and Patchstack entry for current remediation guidance.
- Update the plugin if a fixed version is available from the vendor.
- Restrict plugin administration to trusted users with strong session hygiene.
- Monitor for unexpected Use Any Font API key deactivation.
Validation and detection
- Confirm plugin name and installed version on each WordPress site.
- Verify whether the Use Any Font API key remains active after review.
- Check vulnerability scanners for CVE-2022-27851 coverage.
- Review administrative activity around plugin settings changes.
- Document any sites that cannot be updated immediately.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-27851 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/use-any-font/CVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/use-any-font/wordpress-use-any-font-plugin-6-1-7-cross-site-request-forgery-csrf-vulnerabilityCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.