dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12975

HIGH · 7.2 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 CTX Feed – WooCommerce Product Feed Manager plugin for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the woo_feed_plugin_installing() function in all versions up to, and including, 6.6.11. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to install arbitrary plugins which can be leveraged to achieve remote code execution.

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 CTX Feed – WooCommerce Product Feed Manager plugin for WordPress is vulnerable to broken access control. The woo_feed_plugin_installing() function lacks a capability check, allowing authenticated users with Shop Manager-level permissions to install arbitrary plugins. This arbitrary plugin installation can be leveraged to achieve remote code execution.

MitigationUpdate to version 6.6.12 or later which includes the missing capability check. Until updated, restrict or audit Shop Manager role accounts and consider removing unnecessary administrative users.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Identify CTX Feed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'CTX Feed - WooCommerce Product Feed Manager'. The version number is displayed below the plugin name. Alternatively, check the main plugin file (typically /wp-content/plugins/ctx-feed/ctx-feed.php) for the 'Version' header comment.
    Affected if The installed version is lower than 6.6.12.
  2. List users with Shop Manager role
    In WordPress admin, go to Users > All Users. Filter or scroll to identify users with the 'Shop Manager' role. Note the total count and usernames of Shop Manager accounts.
    Affected if Any user account with Shop Manager role exists and has access to the WordPress admin dashboard.
  3. Verify Shop Manager can access plugin installation
    Log in as a Shop Manager user. Navigate to CTX Feed settings or any area where plugin installation features may appear. Attempt to access the plugin installation functionality (for example, check if a plugin installer or 'Install Plugin' option is visible within the CTX Feed settings pages).
    Affected if The Shop Manager user can see or access options to install/update plugins, particularly within the CTX Feed plugin interface.
  4. Review active plugins for unexpected additions
    In WordPress admin, go to Plugins > Installed Plugins. Look for any recently added or unfamiliar plugins that were not intentionally installed by administrators. Note the activation date and author.
    Affected if Unexpected plugins appear that were not installed by an Administrator, suggesting possible exploitation.

You are affected if the CTX Feed plugin version is below 6.6.12 AND any user with Shop Manager role exists with access to the WordPress admin area.

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 version 6.6.12 or later which includes the missing capability check. Until updated, restrict or audit Shop Manager role accounts and consider removing unnecessary administrative users.

Recommended fix Moderate confidence

CTX Feed – WooCommerce Product Feed Manager version 6.6.12 or later

  1. Log in to the WordPress admin dashboard with administrator privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'CTX Feed – WooCommerce Product Feed Manager' in the plugin list
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  5. Verify the updated version is 6.6.12 or higher
  6. Test that the plugin functionality works as expected 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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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