HomeWordPress vulnerabilitiesLogo Manager For Enamad
Logo Manager For Enamad vulnerabilities
Logo Manager For Enamad has 3 known vulnerabilities in this database. The most recent published record is dated 20 May 2026.
- Known vulnerabilities
- 3
- Active installs
- 5,000+
- Latest version
- 0.7.5
- Last updated
- 28 May 2026
- Most recent
- 20 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-6549 | Medium 6.4 | Up to 0.7.4 | Fixed in a later version (latest 0.7.5) | 20 May 2026 |
| Cross-site scripting (XSS) CVE-2024-5170 | Medium 4.8 | Up to 0.7.1 | Fixed in a later version (latest 0.7.5) | 17 Sep 2024 |
| Cross-site scripting (XSS) CVE-2024-4757 | High 8.1 | Up to 0.7 | Fixed in a later version (latest 0.7.5) | 25 Jun 2024 |
Read the published descriptions
- CVE-2026-6549, 20 May 2026
- 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. CVE record
- CVE-2024-5170, 17 Sep 2024
- The Logo Manager For Enamad WordPress plugin through 0.7.1 does not sanitise and escape in its widgets settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2024-4757, 25 Jun 2024
- The Logo Manager For Enamad WordPress plugin through 0.7.0 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack CVE record
What to do if you run Logo Manager For Enamad
If you run Logo Manager For Enamad, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Logo Manager For Enamad vulnerabilities
Free. We email you when a new vulnerability is published for Logo Manager For Enamad, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.