CVE-2024-5170 json
Logo Manager For Enamad <= 0.7.1 - Admin+ Stored XSS via Widget
published 2y ago modified 4mo ago also EUVD-2024-46419
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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)
Is CVE-2024-5170 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/37b5ed06-0633-49e0-b47d-8aa2f4510179/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L |
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L |
Affected products
- Unknown Logo Manager For Enamad
- logo_manager_for_enamad logo_manager_for_enamad
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/37b5ed06-0633-49e0-b47d-8aa2f4510179/
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2024-5170
- NVD CVE-2024-5170
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.