CVE-2024-4404

ElementsKit PRO <= 3.6.1 - Authenticated (Contributor+) Server-Side Request Forgery

2024-06-13 00:00
Ngô Thiên An (ancorn_)

Strategic Overview

Status
Patched in 3.6.3
Affected Plugin
ElementsKit Pro
Affected Version
<= 3.6.2
CVSS
8.5High
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2024-4404
View all ElementsKit Pro vulnerabilities

At a glance

CVE-2024-4404 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the ElementsKit Pro WordPress plugin, affecting versions <= 3.6.2. It carries a CVSS score of 8.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.6.3; sites on affected versions should update now. Disclosed June 2024, reported by Ngô Thiên An (ancorn_).

Vulnerability Overview

The ElementsKit PRO plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 3.6.2 via the 'render_raw' function. This can allow authenticated attackers, with contributor-level permissions and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-918: Server-Side Request Forgery (SSRF)

ElementsKit Pro <= 3.6.2 carries this weakness at render_raw, and reaching it takes an account at Contributor level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For ElementsKit Pro the fix is 3.6.3: builds <= 3.6.2 are affected, anything from 3.6.3 onward is not.

Remediation

Update to version 3.6.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ElementsKit Pro 3.6.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-4404https://www.wordfence.com/threat-intel/vulnerabilities/id/6417269d-3d49-4f33-b92a-5aacb052bab0https://nvd.nist.gov/vuln/detail/CVE-2024-4404

Related records

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