Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account
-
ExploitSend crafted input to vulnerable plugin endpoint
-
ExecutionInjected SQL executes against database
-
ImpactExfiltrate password hashes and secrets
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account with at least Contributor role on a WordPress site running Product Feed Manager (best-woocommerce-feed) version 7.12.0 or earlier; exploitation is remote (AV:N), low-complexity (AC:L), and needs no user interaction (UI:N). The practical limiting factor is the Contributor-level authentication (PR:L): risk is elevated on sites that allow open user registration or grant Contributor/author roles broadly, and substantially lower on single-admin sites where low-privilege accounts do not exist. No non-default plugin configuration is stated as required. |
| Impact | This is an authenticated SQL injection (CWE-89) requiring at least Contributor-level access to the WordPress site, confirmed by the CVSS vector's PR:L and the description's explicit 'Contributor' qualifier. The Patchstack CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L, base 8.5) reflects network-reachable, low-complexity exploitation with high confidentiality loss and a claimed scope change. No EPSS score, no CISA KEV listing, and no public exploit code are present in the provided data, so exploitation status is 'no public exploit identified at time of analysis' - the 8.5 is a severity rating, not evidence of active abuse. The real-world priority is moderate rather than urgent: exploitation is gated behind a valid Contributor account, which is a meaningful barrier on well-managed sites but trivial on sites with open registration or loose role assignment. Two signals warrant scrutiny: Patchstack's S:C (scope change) is questionable for a WordPress-internal DB query where the database is the same security authority, and I:N is unusual for SQLi (injection often permits writes as well as reads); these vendor choices are not independently verifiable from the single reference. Overall: a genuinely high-severity flaw for multi-author sites, but the authentication requirement and absence of any exploitation/EPSS/KEV signal place it below internet-facing unauthenticated criticals in triage order. |
| Exploit ScenarioDerived | An attacker who holds or registers a Contributor account on a WordPress site running Product Feed Manager <= 7.12.0 submits a crafted parameter to a plugin endpoint that concatenates input into a SQL query, extracting sensitive database contents such as user password hashes, secret keys, or other users' private data. No public proof-of-concept is identified in the provided data, and exploitation requires valid low-privilege authentication (PR:L) but no user interaction and low complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 17, 2026
Authenticated SQL injection in the Rextheme Product Feed Manager WordPress plugin (slug best-woocommerce-feed) affects all versions up to and including 7.12.0 and lets an attacker with at least Contributor-level access on the site inject arbitrary SQL through the plugin's query handling. The reported CVSS 3.1 base score is 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L), with the assessed vector refining this to AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, so the dominant impact is high-confidentiality database disclosure rather than full site takeover. Exploitation requires a low-privileged authenticated account, which makes the risk significantly higher on sites with open registration or broadly granted Contributor/Author roles and much lower on single-admin sites; no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
RemediationAI
No vendor-released patched version is identified in the available data for CVE-2026-66580, so the first action is to check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/best-woocommerce-feed/vulnerability/wordpress-product-feed-manager-plugin-7-12-0-sql-injection-vulnerability and the plugin's update channel for a fixed release, applying it as soon as one is published; if a patched build above 7.12.0 becomes available, upgrading is the definitive fix. Until then, the highest-value compensating control is eliminating the prerequisite: disable open user registration, audit and demote or remove any Contributor/Author accounts that do not need to exist, and tighten role-management plugins so untrusted users cannot obtain Contributor privileges, accepting that this restricts legitimate multi-author workflows. On sites that do not require product feeds, deactivate the Product Feed Manager plugin entirely, which removes the attack surface at the cost of losing feed functionality; if the plugin must stay active, block or rate-limit access to the plugin's feed and AJAX endpoints (for example via server-level rules or a WAF) so that only trusted IPs and administrators can reach them, understanding that IP-based restrictions can break feed scheduling and CDN or marketplace fetchers. Deploying WAF rules tuned for SQL-injection patterns in query strings and POST bodies adds detection but is not a substitute for removing the low-privileged accounts the attack depends on.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic SQL injection (CWE-89) in a WordPress WooCommerce product-feed plugin, where user-influenced input is concatenated into a database query instead of being passed through parameterized statements such as $wpdb->prepare() with placeholders. Product Feed Manager builds and serves WooCommerce product feeds (product titles, prices, stock, categories, custom attributes) and exposes configuration and data-retrieval paths that Contributors can reach, so the injection point sits in the plugin's own query-construction logic rather than in WordPress core. The CPE string cpe:2.3:a:rextheme:product_feed_manager:*:*:*:*:*:*:*:* confirms the vendor/product identity as Rextheme's Product Feed Manager, tracked in ENISA EUVD as EUVD-2026-81501 and reported by Patchstack. The unusual aspects of the published vector - scope change (S:C) and zero integrity impact - are not corroborated by the independent assessment, which treats the impact as confined to the vulnerable component (S:U) with high confidentiality loss and a limited integrity effect, consistent with a read-oriented injection reachable by an authenticated low-privilege user via network requests without user interaction.
Know when Product Feed Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Contributor auth gives PR:L; SQLi reads sensitive DB data (C:H) with possible limited writes (I:L); I treat the DB as the same authority so S:U rather than vendor's S:C.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor SQL Injection in Product Feed Manager <= 7.12.0 versions.
Executive ViewAI
The Rextheme Product Feed Manager WordPress plugin, which powers product feeds for WooCommerce, suffers from a high-severity authenticated SQL injection that could let a Contributor-level user extract sensitive database information. Organizations with open user registration or broad Contributor/Author assignments face significant exposure to data breaches, regulatory scrutiny, and reputational damage. No vendor-released patch identified at time of analysis, and no public exploit identified at time of analysis, but immediate mitigation is warranted.
Disable the Product Feed Manager plugin until a patch is released; restrict Contributor and Author capabilities to trusted users only; deploy WAF rules to detect and block SQL injection patterns targeting the plugin; monitor database and user activity for signs of unauthorized access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-81501
GHSA-96q9-52c8-47xj
NVD
CVE.org
EPSS
Exploit-DB