Skip to main content
CVE-2023-5877VulnerabilityPublished Updated

CVE-2023-5877: affiliate-toolkit (WordPress plugin) · Server-Side Request Forgery (SSRF)

Affects affiliate-toolkit (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Unknown affiliate-toolkitAffected
  • =0
Fixed in–

AI-suggested

Immediate mitigation steps include: 1) Upgrading the affiliate-toolkit plugin to version 3.4.3 or later once available, as this version addresses the vulnerability by implementing proper authorization and authentication controls. 2) If an official patch is not yet available, temporarily disabling or removing the affiliate-toolkit plugin to eliminate exposure. 3) Implementing web application firewall (WAF) rules to block requests to the atkp_imagereceiver.php endpoint or to restrict outbound HTTP requests from the web server to internal IP ranges. 4) Restricting server-side HTTP requests to internal network addresses via network-level controls or application-level allowlists to prevent SSRF exploitation. 5) Monitoring web server logs for unusual requests targeting the vulnerable endpoint and for outbound connections to internal IPs. 6) Conducting internal network segmentation to limit the impact of SSRF by isolating critical systems from the web server. 7) Reviewing and hardening WordPress security configurations and ensuring minimal plugin usage to reduce attack surface.

Description

The affiliate-toolkit WordPress plugin before 3.4.3 lacks authorization and authentication for requests to it's affiliate-toolkit-starter/tools/atkp_imagereceiver.php endpoint, allowing unauthenticated visitors to make requests to arbitrary URL's, including RFC1918 private addresses, leading to a Server Side Request Forgery (SSRF) issue.

References

Community reviews

Loading reviews…