CVE-2024-4757

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

2024-06-04 00:00
Bob Matyas

Strategic Overview

Status
Patched in 0.7.1
Affected Version
<= 0.7.0
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-4757
View all Logo Manager For Enamad – لوگوی نماد الکترونیکی vulnerabilities

At a glance

CVE-2024-4757 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Logo Manager For Enamad WordPress plugin, affecting versions <= 0.7.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.7.1; sites on affected versions should update now. Disclosed June 2024, reported by Bob Matyas.

Vulnerability Overview

The Logo Manager For Enamad plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.7.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update plugin settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Logo Manager For Enamad <= 0.7.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Logo Manager For Enamad the fix is 0.7.1: builds <= 0.7.0 are affected, anything from 0.7.1 onward is not.

Remediation

Update to version 0.7.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Logo Manager For Enamad: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Logo Manager For Enamad 0.7.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C