CVE-2026-6415 MEDIUM

CVE-2026-6415: Advanced Custom Fields: Font Awesome Field <= 5.0.2 - Authenticated (Subscriber+) Stored Cross-Site Scripting via JSON Field

Vendor Justinkruit
Product Advanced Custom Fields: Font Awesome Field
Weakness CWE-79 · XSS
Published May 15, 2026
Last update May 15, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The Advanced Custom Fields: Font Awesome Field plugin for WordPress contains a cross-site scripting (XSS) vulnerability in versions up to 5.0.2. An authenticated user with low privileges can inject malicious scripts that execute in other users' browsers, including site administrators. The vulnerability has a changed scope, meaning the impact extends beyond the vulnerable component itself.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that runs in other users' browsers, potentially stealing session tokens or performing actions as those users.

Potential impact on your site

04Site Impact

Authenticated users can inject scripts affecting other site visitors and admins; could lead to account compromise or unauthorized site modifications.

Conditions required to exploit

05Prerequisites

Attacker must have a WordPress user account with low-level privileges (e.g., contributor or subscriber role).

Key dates

06Disclosure timeline

May 15, 2026 CVE published
May 15, 2026 Record updated