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

CVE-2026-49044

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

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Justin Kruit Advanced Custom Fields: Font Awesome Field allows Stored XSS. This issue affects Advanced Custom Fields: Font Awesome Field: from n/a through 5.0.2.

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

Stored Cross-site Scripting (XSS) vulnerability in the Advanced Custom Fields: Font Awesome Field WordPress plugin. User-supplied input in the Font Awesome field is not properly sanitized before being stored and rendered in web pages, allowing authenticated attackers to inject malicious JavaScript that executes when other users view the affected content.

MitigationUpdate the plugin to the latest version beyond 5.0.2 once available; implement proper input sanitization using WordPress escaping functions (esc_html(), esc_attr(), wp_kses()) on all field outputs.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Advanced Custom Fields: Font Awesome Field' in the list
    Affected if The plugin is present in the WordPress installation
  2. Check the installed version
    On the Plugins page, find the version number listed for 'Advanced Custom Fields: Font Awesome Field'
    Affected if The version is 5.0.2 or lower (versions up to and including 5.0.2 are affected)
  3. Identify if Font Awesome field is in use
    Go to Custom Fields > Field Groups and examine any field groups; check if any field has 'Field Type' set to 'Font Awesome' or similar
    Affected if A Font Awesome field is configured and being used to accept user input
  4. Inspect stored field values for XSS payloads
    Query the wp_postmeta table (or use a plugin like WP Data Access) to examine values stored in fields associated with Font Awesome; look for script tags, javascript:, or other HTML/script content in the meta_value column
    Affected if Any stored meta_value contains unsanitized HTML or script tags that could execute in a browser

A user is affected if the plugin is installed with version 5.0.2 or lower AND the Font Awesome field type is actively storing user input that has not been escaped.

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

Update the plugin to the latest version beyond 5.0.2 once available; implement proper input sanitization using WordPress escaping functions (esc_html(), esc_attr(), wp_kses()) on all field outputs.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49044 — 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-49044 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