CVE-2026-32443
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Josh Kohlbach Product Feed PRO for WooCommerce woo-product-feed-pro allows Cross Site Request Forgery.This issue affects Product Feed PRO for WooCommerce: from n/a through <= 13.5.2.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the Product Feed PRO for WooCommerce plugin allows attackers to trick authenticated administrators into performing unintended actions such as modifying feed configurations, export settings, or other administrative functions without their consent.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Product Feed PRO for WooCommerce is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Product Feed PRO for WooCommerce' in the listAffected if Plugin is present in the plugins list regardless of activation status
-
Identify the installed plugin versionIn the plugins list, locate the version number displayed beneath the plugin name 'Product Feed PRO for WooCommerce'Affected if Version cannot be determined or is unknown
-
Inspect admin forms for nonce token fieldsRight-click any admin page within the Product Feed PRO plugin (such as feed configuration or export settings) and view the page source. Search for HTML input elements with type='hidden' containing names like 'nonce', '_wpnonce', or 'security'Affected if State-changing forms (add/edit feed, modify settings, export) lack hidden nonce fields
-
Verify nonce validation in plugin codeAccess the plugin files via wp-content/plugins/pirate-woo-product-feed or similar path, then search PHP files for 'wp_verify_nonce', 'check_admin_referer', or 'wp_nonce_field' function calls on admin action handlersAffected if No nonce validation functions are found in the plugin's PHP handlers for administrative actions
-
Check for Origin or Referer header validationIn the plugin's PHP request handlers, search for server variable checks such as '$_SERVER[\'HTTP_ORIGIN\']' or '$_SERVER[\'HTTP_REFERER\']' being validated before processing state-changing requestsAffected if No Origin or Referer header validation is performed before executing admin actions
If the plugin is installed and its admin forms lack nonce token fields (or the code does not validate them), the environment is affected by this CSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and verify Origin/Referer headers to prevent forged requests.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32443 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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