Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14983: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in mattkeys Advanced Custom Fields: Font Awesome Field

0
Medium
VulnerabilityCVE-2025-14983cvecve-2025-14983cwe-79
Published: Thu Feb 19 2026 (02/19/2026, 04:36:22 UTC)
Source: CVE Database V5
Vendor/Project: mattkeys
Product: Advanced Custom Fields: Font Awesome Field

Description

The Advanced Custom Fields: Font Awesome Field plugin for WordPress is vulnerable to Cross-Site Scripting in all versions up to, and including, 5.0.1 due to insufficient input sanitization and output escaping. This makes it possible forauthenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts that execute in a victim's browser.

AI-Powered Analysis

AILast updated: 02/19/2026, 05:15:35 UTC

Technical Analysis

CVE-2025-14983 identifies a Cross-Site Scripting (XSS) vulnerability in the Advanced Custom Fields: Font Awesome Field plugin for WordPress, maintained by mattkeys. The vulnerability exists in all versions up to and including 5.0.1 due to insufficient sanitization of user inputs and lack of proper output escaping during web page generation. This flaw allows authenticated users with Contributor-level access or higher to inject arbitrary JavaScript code into the plugin's fields. When other users view the affected pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or data theft. The vulnerability is categorized under CWE-79 and has a CVSS v3.1 base score of 6.4, indicating medium severity. The attack vector is network-based with low attack complexity, requiring privileges but no user interaction. The scope is changed, meaning the vulnerability can affect resources beyond the vulnerable component. Currently, no public exploits or patches are available, but the vulnerability is publicly disclosed and documented by Wordfence. The flaw primarily threatens confidentiality and integrity of user data and site content but does not impact availability. The vulnerability is particularly concerning for multi-user WordPress environments where contributors can add or edit content, as it enables cross-user script injection.

Potential Impact

For European organizations, this vulnerability poses a significant risk to websites using the Advanced Custom Fields: Font Awesome Field plugin, especially those with multiple user roles including Contributors or higher. Exploitation could lead to unauthorized script execution in browsers of site administrators or other users, resulting in session hijacking, theft of sensitive information, or unauthorized actions performed on behalf of victims. This undermines trust in the affected websites and can lead to data breaches or defacement. Organizations in sectors such as e-commerce, government, education, and media, which often rely on WordPress with multiple contributors, are particularly vulnerable. The impact extends to brand reputation, regulatory compliance (e.g., GDPR), and potential financial losses. Since the vulnerability requires authenticated access, insider threats or compromised contributor accounts increase risk. The lack of known exploits currently reduces immediate threat but does not eliminate the risk of future attacks.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should immediately audit user roles and permissions, restricting Contributor-level access to trusted users only. Implement strict input validation and output encoding on all user-generated content fields, especially those related to the Font Awesome Field plugin. Monitor logs for unusual contributor activity or unexpected script injections. Employ Web Application Firewalls (WAFs) with rules targeting XSS payloads specific to this plugin. Since no official patch is currently available, consider temporarily disabling or removing the vulnerable plugin if feasible. Educate content contributors about safe input practices and the risks of injecting scripts. Regularly update WordPress core and plugins to the latest versions once patches are released. Conduct penetration testing focusing on XSS vectors within multi-user environments. Finally, implement Content Security Policy (CSP) headers to reduce the impact of potential script injections.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-19T17:53:53.254Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699697f46aea4a407a3be0a5

Added to database: 2/19/2026, 4:56:20 AM

Last enriched: 2/19/2026, 5:15:35 AM

Last updated: 2/21/2026, 12:20:26 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats