dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-6415

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Advanced Custom Fields: Font Awesome plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 5.0.2. This is due to insufficient input validation of JSON field values and unsafe client-side HTML construction in the update_preview() JavaScript function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Advanced Custom Fields: Font Awesome WordPress plugin (versions up to 5.0.2) contains a stored XSS vulnerability. Attackers with Subscriber-level access can inject malicious scripts through insufficiently validated JSON field values that are unsafely rendered in the update_preview() JavaScript function, causing scripts to execute on page load for all visitors.

MitigationUpgrade to a version newer than 5.0.2 when available, or apply input sanitization to all JSON field values and refactor update_preview() to use safe DOM methods instead of unsafe HTML construction.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation and activation status
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Advanced Custom Fields: Font Awesome' or check via wp-cli: wp plugin list --status=active --name='acf-font-awesome'
    Affected if Plugin is installed and active, exposing the vulnerable code
  2. Identify installed plugin version
    Check the plugin version in the plugin header (WP admin Plugins page or file /wp-content/plugins/acf-font-awesome/readme.txt) and compare to 5.0.2
    Affected if Version is 5.0.2 or lower (any version up to and including 5.0.2)
  3. Determine if ACF JSON field types are in use
    Review ACF field groups in wp-admin > Custom Fields, or query wp_posts for posts with post_type='acf-field-group' containing field type 'fontawesome' or custom JSON field configurations
    Affected if Any field group uses Font Awesome or JSON-based custom fields that feed into update_preview()
  4. Verify low-privilege user access to field editing
    Check user roles with Subscriber level access (wp_users + wp_usermeta for role capability 'edit_posts') who could potentially create or modify field values
    Affected if Subscriber-level or higher users can access and save field data that flows to the vulnerable function
  5. Inspect update_preview() function accessibility
    Search plugin source code (particularly /js/input.js or similar frontend/admin scripts) for the update_preview() function and verify it handles raw JSON field output without sanitization
    Affected if update_preview() function exists and constructs HTML from unsanitized field values

You are affected if the Font Awesome ACF plugin versions up to 5.0.2 is active, uses JSON-based fields, and the update_preview() function is accessible to render unsanitized user input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version newer than 5.0.2 when available, or apply input sanitization to all JSON field values and refactor update_preview() to use safe DOM methods instead of unsafe HTML construction.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6415 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6415 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data