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

CVE-2026-2496

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
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 Ed's Font Awesome plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `eds_font_awesome` shortcode in all versions up to, and including, 2.0. This is due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-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

Stored XSS vulnerability in Ed's Font Awesome WordPress plugin versions up to 2.0. The plugin's `eds_font_awesome` shortcode fails to properly sanitize and escape user-supplied attributes, allowing authenticated contributors and above to inject persistent malicious scripts that execute when users view affected pages.

MitigationUpdate the plugin to version 2.1 or later which includes proper input sanitization and output escaping. Audit existing content for injected scripts and consider restricting shortcode usage permissions until patched.

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. Verify Ed's Font Awesome plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ed's Font Awesome' in the list, or check the plugins directory at /wp-content/plugins/ for a folder named 'font-awesome' or similar
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Ed's Font Awesome, and note the version number displayed under the plugin name
    Affected if Version is 2.0 or earlier (the vulnerable version range)
  3. Identify usage of the eds_font_awesome shortcode
    Search your WordPress posts, pages, and custom post types for occurrences of the [eds_font_awesome] shortcode by querying the wp_posts table or using a plugin that searches shortcode usage
    Affected if The shortcode is present in any published content
  4. Inspect shortcode attributes for unsanitized input
    Examine the shortcode syntax in your content, for example [eds_font_awesome icon="user"], and check if any attributes contain special characters like < > " ' or JavaScript event handlers that could indicate injected scripts
    Affected if Shortcode attributes contain unsanitized user-supplied values that could execute as JavaScript

You are affected if Ed's Font Awesome plugin version 2.0 or earlier is installed AND the eds_font_awesome shortcode is used in your content with potentially malicious attributes.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.1 or later which includes proper input sanitization and output escaping. Audit existing content for injected scripts and consider restricting shortcode usage permissions until patched.

Recommended fix Moderate confidence

Version 2.1 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Ed's Font Awesome' plugin
  4. 4. Check if an update is available and update to the latest version
  5. 5. If no update is visible in WordPress, manually download the latest version from wordpress.org/plugins/eds-font-awesome/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 2.1 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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