dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-3499

HIGH · 8.8 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Product Feed PRO for WooCommerce by AdTribes – Product Feeds for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions 13.4.6 through 13.5.2.1. This is due to missing or incorrect nonce validation on the ajax_migrate_to_custom_post_type, ajax_adt_clear_custom_attributes_product_meta_keys, ajax_update_file_url_to_lower_case, ajax_use_legacy_filters_and_rules, and ajax_fix_duplicate_feed functions. This makes it possible for unauthenticated attackers to trigger feed migration, clear custom-attribute transient caches, rewrite feed file URLs to lowercase, toggle legacy filter and rule settings, and delete duplicated feed posts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Product Feed PRO for WooCommerce plugin versions 13.4.6 through 13.5.2.1 lacks proper nonce validation on five AJAX endpoints (ajax_migrate_to_custom_post_type, ajax_adt_clear_custom_attributes_product_meta_keys, ajax_update_file_url_to_lower_case, ajax_use_legacy_filters_and_rules, and ajax_fix_duplicate_feed). This allows unauthenticated attackers to forge administrative requests by tricking logged-in admins into clicking malicious links, enabling unauthorized feed migrations, cache clearing, URL modifications, settings toggles, and feed deletion.

MitigationUpdate to the latest plugin version and ensure all AJAX actions implement proper nonce verification using wp_verify_nonce() or check_admin_referer() before processing requests.

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Product Feed PRO for WooCommerce and note the version number displayed, or check the plugin header in the main plugin file (usually in wp-content/plugins/woobox-product-feed-pro/product-feed-pro-for-woocommerce.php or similar)
    Affected if version is 13.4.6, 13.4.7, 13.4.8, 13.4.9, 13.5.0, 13.5.1, 13.5.2, or 13.5.2.1 (any version from 13.4.6 through 13.5.2.1)
  2. Confirm plugin is active
    Verify the Product Feed PRO for WooCommerce plugin is currently activated on the site through Plugins > Installed Plugins
    Affected if the plugin is installed and active, making the vulnerable AJAX endpoints accessible
  3. Identify vulnerable AJAX endpoint registration
    Examine the main plugin PHP file for the presence of add_action calls registering the following: wp_ajax_ajax_migrate_to_custom_post_type, wp_ajax_ajax_adt_clear_custom_attributes_product_meta_keys, wp_ajax_ajax_update_file_url_to_lower_case, wp_ajax_ajax_use_legacy_filters_and_rules, wp_ajax_ajax_fix_duplicate_feed (or their nopriv variants)
    Affected if any of these five AJAX actions are registered without a corresponding nonce check function (such as check_ajax_referer or wp_verify_nonce) in the handler callback

You are affected if the Product Feed PRO for WooCommerce plugin is active and running version 13.4.6 through 13.5.2.1 with the vulnerable AJAX endpoints present and lacking nonce validation.

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 plugin version and ensure all AJAX actions implement proper nonce verification using wp_verify_nonce() or check_admin_referer() before processing requests.

Recommended fix Moderate confidence

13.5.3 or later

  1. Locate the Product Feed PRO for WooCommerce plugin in the WordPress admin dashboard under Plugins
  2. Deactivate the current version of the plugin
  3. Delete the current version of the plugin
  4. Navigate to Plugins > Add New > Upload Plugin
  5. Upload and install the latest version of Product Feed PRO for WooCommerce (version 13.5.3 or later)
  6. Activate the new version of the plugin
  7. Verify that the plugin is functioning correctly by accessing the Product Feed PRO settings

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-2026-3499 — 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-2026-3499 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