CVE intelligence and bounded remediation

CVE-2021-24977 — Dineshkarki Use Any Font security vulnerability

Medium CVSS 6.1

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 escaping in the backend, it could also lead to Stored XSS issues

Severity
Medium
CVSS
6.1 (3.1)
Published
2022-02-28
CISA KEV
Not currently listed
Ecosystem
php/wordpress
Weaknesses
CWE-862

Affected products

  • dineshkarki / use_any_font

Matched remediation archetype

Authorization bypass, IDOR, and cross-tenant access

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map object and action authorization checks across API, UI, batch, import/export, and background-job paths.
  • Identify tenant, ownership, role, and policy boundaries for affected resources and administrative operations.
  • Use synthetic fixtures to compare intended access matrices without accessing another user's real data.

Remediate safely

  • Enforce server-side authorization at each resource access and state transition using the authenticated principal and trusted tenant context.
  • Scope data queries by tenant and ownership; treat client-supplied identifiers, roles, and policy claims as untrusted.
  • Add deny-by-default policy tests for horizontal and vertical access across every affected transport.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.