Skip to main content
VulnerabilityPublished Updated

CVE-2024-8393: Woocommerce Blocks (WordPress plugin) · PHP Remote File Inclusion

Affects Woocommerce Blocks (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 6.6 Medium.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Aug 2025

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
delabon Woocommerce Blocks – WoolookAffected
  • =0
Fixed in–

AI-suggested

Until an official fix is released, restrict administrator access to trusted users only and monitor for suspicious activity. Consider disabling or removing the vulnerable plugin if feasible. Implementing CSRF protections may reduce risk but does not fully mitigate the vulnerability.

Description

The Woocommerce Blocks – Woolook plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.7.0 via the via the 'tab' parameter. This makes it possible for authenticated attackers, with Administrator-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. Please note that this can also be exploited via CSRF techniques.

References

Community reviews

Loading reviews…