dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31377

HIGH · 7.5 CVSS v3.1 Published 2025-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Missing Authorization vulnerability in Asaquzzaman mishu Woo Product Feed For Marketing Channels woocommerce-to-google-merchant-center allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Woo Product Feed For Marketing Channels: from n/a through <= 1.9.0.

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 confidence

Missing authorization vulnerability in the Woo Product Feed For Marketing Channels WordPress plugin allows unauthenticated or low-privileged users to access sensitive functionality or data that should require higher-level permissions. The plugin fails to implement proper capability checks before executing administrative or marketing-related functions, enabling attackers to exploit incorrectly configured access control security levels.

MitigationApply available vendor patch or update to the latest version immediately. Until patched, restrict administrative access to the WordPress dashboard and disable the plugin if not actively needed.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Woo Product Feed For Marketing Channels' or check the plugins directory /wp-content/plugins/ for a folder containing 'woo-product-feed' or similar
    Affected if The plugin is installed and active
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin name to view its details, or open the main plugin PHP file and look for the 'Version:' header in the plugin comment block
    Affected if You cannot determine the version or are running a version within the known vulnerable range
  3. Compare version to affected range
    Cross-reference your installed version number with the CVE-advisory documented vulnerable version range (contact vendor security advisory or national CVE database for specific version bounds)
    Affected if Your installed version falls within the vulnerable version range
  4. Verify user role access controls
    As an administrator, navigate to the plugin settings page and check if WordPress roles (subscriber, contributor, author, editor) can access marketing channel export or feed generation features that should be restricted to administrators only
    Affected if Lower-privileged users (subscriber, contributor, author) can access administrative or marketing export functions without elevated permissions
  5. Test unauthenticated access to plugin endpoints
    Use a browser or HTTP tool to access plugin AJAX actions or direct PHP files in the plugin directory without logging in (e.g., check if /wp-admin/admin-ajax.php?action=xxx exposes marketing data)
    Affected if Unauthenticated requests return sensitive marketing data or trigger administrative functions

Your environment is affected if the Woo Product Feed For Marketing Channels plugin is installed, runs a version within the vulnerable range, AND allows low-privileged or unauthenticated users to access administrative or marketing functions that should require higher permissions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available vendor patch or update to the latest version immediately. Until patched, restrict administrative access to the WordPress dashboard and disable the plugin if not actively needed.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31377 — 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-31377 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