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

CVE-2026-6549

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-20
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 Logo Manager For Enamad plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title' attribute of the `vc_enamad_namad`, `vc_enamad_shamed`, and `vc_enamad_custom` shortcodes in all versions up to, and including, 0.7.4 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

The Logo Manager For Enamad WordPress plugin up to version 0.7.4 suffers from a stored XSS vulnerability in three shortcodes (vc_enamad_namad, vc_enamad_shamed, vc_enamad_custom). The 'title' attribute in these shortcodes is not sanitized on input or escaped on output, allowing authenticated contributors+ to inject malicious JavaScript that executes when other users view affected pages.

MitigationUpdate the plugin to a version beyond 0.7.4 that implements proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr) for the title attribute in the affected shortcodes.

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 Logo Manager For Enamad plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Logo Manager For Enamad' or check wp-content/plugins directory for the plugin folder
    Affected if The plugin is present and active in the WordPress installation
  2. Check the installed plugin version
    View the plugin main file header (usually filename.php in the plugin directory) or check the Plugins page in WordPress admin for the version number
    Affected if Version is unknown or earlier than the patched version that includes esc_attr() sanitization for the title attribute
  3. Identify use of vulnerable shortcodes
    Search WordPress database (wp_posts table) or use a plugin to search post content for shortcodes: [vc_enamad_namad], [vc_enamad_shamed], [vc_enamad_custom]
    Affected if Any of these three shortcodes are present in published content
  4. Check if title attribute is used in shortcodes
    Examine the shortcode usage in post content to see if title= attribute is present, for example [vc_enamad_namad title="value"]
    Affected if The shortcode includes a title attribute with user-controlled or unsanitized content

A user is affected if the Logo Manager For Enamad plugin is installed, uses a version prior to proper sanitization, and has any of the three vulnerable shortcodes (vc_enamad_namad, vc_enamad_shamed, vc_enamad_custom) with a title attribute in published content.

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 a version beyond 0.7.4 that implements proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_attr) for the title attribute in the affected shortcodes.

Recommended fix Moderate confidence

Latest version after 0.7.4 (check wordpress.org for current release)

  1. 1. Log in to the WordPress admin dashboard with contributor-level or higher privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Logo Manager For Enamad' plugin in the list
  4. 4. Check if an update is available - if so, update to the latest version
  5. 5. If no update is shown in the dashboard, manually download the latest version from wordpress.org/plugins/logo-manager-for-enamad/ and reinstall
  6. 6. After updating, verify that the plugin is functioning correctly on the site
  7. 7. Clear any caching layers if the site uses caching

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 / QA2.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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