CVE-2024-5170: The Logo Manager For Enamad WordPress plugin through 0.7.1 does not sanitise and escape in its widgets setting

Q: How do I fix CVE-2024-5170?

logo manager for enamad: upgrade to newer than 0.7.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-5170 being exploited?

CVE-2024-5170 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-5170 affect?

CVE-2024-5170 affects logo manager for enamad. Severity is medium (CVSS 4.8). 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_ht

Q: How urgent is CVE-2024-5170?

Priority 28/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2024-5170 is a medium-severity flaw (CVSS 4.8) affecting logo manager for enamad. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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)

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-09-17
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp-master

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-09-17 06:15 UTCPublished CVE record published
2026-06-17 08:15 UTCUpdated Record last modified

wp-master logo manager for enamad UPGRADE

Affected: <= 0.7.1

Fixed in: newer than 0.7.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy logo-manager-for-enamad || rpm -q logo-manager-for-enamad || logo-manager-for-enamad --version

2. UPGRADE to newer than 0.7.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade logo-manager-for-enamad

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade logo-manager-for-enamad

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-5170?

logo manager for enamad: upgrade to newer than 0.7.1. Exact commands for each OS are on this page.

Is CVE-2024-5170 being exploited?

CVE-2024-5170 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-5170 affect?

CVE-2024-5170 affects logo manager for enamad. Severity is medium (CVSS 4.8). 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_ht

How urgent is CVE-2024-5170?

Priority 28/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-4757 HIGH 8.1 UPGRADE The Logo Manager For Enamad WordPress plugin through 0.7.0 does not have CSRF check in some places, and is mis

References

← Back to latest CVEs