What is the CVSS score of CVE-2026-6549?

CVE-2026-6549 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Logo Manager Enamad CVE-2026-6549

EUVD-2026-31042 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-05-20 Wordfence

GHSA-jxx5-9gww-wrxc

WordPress XSS Wordpress Plugin Logo Manager For Enamad

6.4

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

6.4 MEDIUM

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

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

May 20, 2026 - 02:37 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Stored Cross-Site Scripting in the Logo Manager For Enamad WordPress plugin (versions up to and including 0.7.4) allows authenticated attackers with contributor-level access to inject persistent malicious scripts via the 'title' attribute of three shortcodes - vc_enamad_namad, vc_enamad_shamed, and vc_enamad_custom. The injected payload executes in the browser of any user who subsequently visits the compromised page, enabling session hijacking, credential theft, or malicious redirects against site visitors and administrators. No public exploit code or active exploitation has been identified at time of analysis; however, the low privilege requirement (contributor) broadens the realistic attacker pool on multi-author WordPress sites.

Technical ContextAI

The affected component is the Logo Manager For Enamad WordPress plugin (vendor: goback2, CPE: cpe:2.3:a:goback2:logo_manager_for_enamad:*:*:*:*:*:*:*:*), which integrates with Visual Composer shortcodes to render Iranian e-trust seal logos (Enamad). The vulnerability resides in widgets.php at line 295, where user-supplied values for the 'title' attribute of the vc_enamad_namad, vc_enamad_shamed, and vc_enamad_custom shortcodes are neither sanitized on input nor escaped on output. CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS) describes this root cause: attacker-controlled data flows from the database to HTML output without encoding, allowing arbitrary JavaScript to be embedded in rendered pages. The CVSS scope is Changed (S:C), reflecting that the injected script executes in the victim's browser context rather than the WordPress application context, crossing a security boundary.

RemediationAI

No specific patched version has been confirmed from the available input data. Site administrators should immediately check the WordPress.org plugin repository (https://wordpress.org/plugins/logo-manager-for-enamad) for an updated release beyond 0.7.4 and apply it if available. The Wordfence threat intelligence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/ed6d1167-c89d-4c97-9446-b968df945e6c?source=cve should be monitored for patch confirmation. As a compensating control pending a patch, administrators should restrict contributor-level account creation and audit existing contributor accounts for legitimacy, since the attack requires that privilege level. Additionally, a Web Application Firewall with WordPress XSS rules (such as Wordfence's own firewall) can block the injection attempt at the request layer, though this does not remediate the underlying flaw. Disabling the affected shortcodes (vc_enamad_namad, vc_enamad_shamed, vc_enamad_custom) in page content if not actively needed eliminates the attack surface without removing the plugin entirely.