CVE-2023-5877

affiliate-toolkit <= 3.4.2 - Unauthenticated Server-Side Request Forgery

2023-12-11 00:00
Yuchen Ji

Strategic Overview

Status
Patched in 3.4.3
Affected Version
<= 3.4.2
CVSS
6.5Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2023-5877
View all affiliate-toolkit – Multi-Network Affiliate & Amazon Product Display vulnerabilities

At a glance

CVE-2023-5877 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the affiliate-toolkit WordPress plugin, affecting versions <= 3.4.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.4.3; sites on affected versions should update now. Disclosed December 2023, reported by Yuchen Ji.

Vulnerability Overview

The affiliate-toolkit – WordPress Affiliate Plugin plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.4.2 via the affiliate-toolkit-starter/tools/atkp_imagereceiver.php endpoint. This makes it possible for unauthenticated attackers 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 privileges on the target site, and no interaction from a victim user.

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

Reaching this weakness in affiliate-toolkit <= 3.4.2 takes no account at all. 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 affiliate-toolkit the fix is 3.4.3: builds <= 3.4.2 are affected, anything from 3.4.3 onward is not.

Remediation

Update to version 3.4.3, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: affiliate-toolkit 3.4.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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