Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

Logo Manager For Enamad – لوگوی نماد الکترونیکی Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with Logo Manager For Enamad – لوگوی نماد الکترونیکی, published between 2024 and 2026.

Dataset last synchronized: 2026-08-02 09:41:47 UTC

At a glance

Security Snapshot

3Total records
0Critical
0High
3Medium
0Low
0Informational
2Patched records
1Currently marked unpatched
2024-06-04First disclosure
2026-05-19Latest disclosure
3 of 3CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202422 records
202611 records

Severity Breakdown

SeverityRecordsShare
Medium3100%

Vulnerability-Type Breakdown

Cross-Site Scripting

2 records66.7%

First: 2024. Latest: 2026.

CSRF

1 record33.3%

First: 2024. Latest: 2024.

Patch Status

Patched
2
Currently marked unpatched
1
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 0.7.3
  • 0.7.1

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-0.7.4Logo Manager For Enamad <= 0.7.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'title' Shortcode AttributeMay 19, 2026Not suppliedMedium
*-0.7.2Logo Manager For Enamad <= 0.7.2 - Authenticated (Admin+) Stored Cross-Site ScriptingAugust 27, 20240.7.3Medium
*-0.7.0Logo Manager For Enamad <= 0.7.0 - Cross-Site Request Forgery to Stored Cross-Site ScriptingJune 4, 20240.7.1Medium

Selected source records

Latest Records

MediumCVE-2026-6549

Logo Manager For Enamad <= 0.7.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'title' Shortcode Attribute

Published: May 19, 2026

Affected versions
*-0.7.4
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-5170

Logo Manager For Enamad <= 0.7.2 - Authenticated (Admin+) Stored Cross-Site Scripting

Published: August 27, 2024

Affected versions
*-0.7.2
Patched versions
0.7.3
Original Wordfence record
MediumCVE-2024-4757

Logo Manager For Enamad <= 0.7.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting

Published: June 4, 2024

Affected versions
*-0.7.0
Patched versions
0.7.1
Original Wordfence record

Highest-Severity Records

MediumCVE-2026-6549

Logo Manager For Enamad <= 0.7.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'title' Shortcode Attribute

Published: May 19, 2026

Affected versions
*-0.7.4
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-4757

Logo Manager For Enamad <= 0.7.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting

Published: June 4, 2024

Affected versions
*-0.7.0
Patched versions
0.7.1
Original Wordfence record
MediumCVE-2024-5170

Logo Manager For Enamad <= 0.7.2 - Authenticated (Admin+) Stored Cross-Site Scripting

Published: August 27, 2024

Affected versions
*-0.7.2
Patched versions
0.7.3
Original Wordfence record

Currently Marked Unpatched Records

MediumCVE-2026-6549

Logo Manager For Enamad <= 0.7.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'title' Shortcode Attribute

Published: May 19, 2026

Affected versions
*-0.7.4
Patched versions
Not supplied
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory