dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-13439

MEDIUM · 5.9 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Fancy Product Designer plugin for WordPress is vulnerable to Information Disclosure and PHAR Deserialization in all versions up to, and including, 6.4.8. This is due to insufficient validation of user-supplied input in the 'url' parameter of the 'fpd_custom_uplod_file' AJAX action, which flows directly into the 'getimagesize' function without sanitization. This makes it possible for unauthenticated attackers to read arbitrary sensitive files from the server, including wp-config.php.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Fancy Product Designer WordPress plugin has an unauthenticated information disclosure vulnerability in versions up to 6.4.8. The 'fpd_custom_uplod_file' AJAX action accepts a 'url' parameter that is passed directly to PHP's getimagesize() function without sanitization, allowing path traversal to read arbitrary files like wp-config.php. The vulnerability also mentions PHAR deserialization via this vector.

MitigationUpdate to the latest patched version of Fancy Product Designer when available. Until then, disable the plugin or restrict access to the fpd_custom_uplod_file AJAX endpoint via firewall rules. Implement input validation with path traversal protection if applying a temporary fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Fancy Product Designer plugin is installed
    Check the WordPress plugins directory or review the plugin list via WP Admin > Plugins. Look for 'Fancy Product Designer' in the installed plugins list.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WP Admin > Plugins, find the Fancy Product Designer entry and read the version number from the plugin details. Alternatively, check the main plugin file (typically /wp-content/plugins/fancy-product-designer/includes/class-fpd-product-designer.php or similar) for the 'Version' header in the file comments.
    Affected if The version number is 6.4.8 or lower
  3. Confirm the plugin is active on the site
    In WP Admin > Plugins, verify that Fancy Product Designer is activated. An inactive plugin may still have files present but would not execute the vulnerable code.
    Affected if The plugin shows as 'Active' in the WordPress admin

The environment is affected if Fancy Product Designer is installed, active, and running version 6.4.8 or lower, with the fpd_custom_uplod_file AJAX endpoint exposed to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of Fancy Product Designer when available. Until then, disable the plugin or restrict access to the fpd_custom_uplod_file AJAX endpoint via firewall rules. Implement input validation with path traversal protection if applying a temporary fix.

Recommended fix High confidence

Fancy Product Designer version 6.4.9 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Fancy Product Designer' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 6.4.9 or later
  5. Verify the update was successful by checking the plugin version after updating
  6. Test the Fancy Product Designer functionality to ensure the plugin still works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13439 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13439 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data