CVE-2025-13231

Fancy Product Designer | WooCommerce WordPress <= 6.4.8 - Unauthenticated Server-Side Request Forgery via Race Condition

Strategic Overview

Status
Patched in 6.5.0
Affected Plugin
Fancy Product Designer
Affected Version
<= 6.4.8
CVSS
6.5Medium
Weakness type
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CVE
CVE-2025-13231
View all Fancy Product Designer vulnerabilities

At a glance

CVE-2025-13231 is a medium-severity Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in the Fancy Product Designer WordPress plugin, affecting versions <= 6.4.8. 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 6.5.0; sites on affected versions should update now. Disclosed December 2025, reported by Muhammad Zeeshan (Xib3rR4dAr).

Vulnerability Overview

The Fancy Product Designer plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.4.8. This is due to a time-of-check/time-of-use (TOCTOU) race condition in the 'url' parameter of the fpd_custom_uplod_file AJAX action. The plugin validates the URL by calling getimagesize() first, then later retrieves the same URL using file_get_contents(). This makes it possible for unauthenticated attackers to exploit the timing gap to perform SSRF attacks by serving a valid image during validation, then changing the response to redirect to arbitrary internal or external URLs during the actual fetch.

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-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Remediation

Update to version 6.5.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Fancy Product Designer 6.5.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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