Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain WordPress Administrator access
-
DeliveryOpen CTX Feed Pro Feed Config field
-
ExploitInject PHP into eval()-bound input
-
ExecutionSave to trigger evaluation
-
ImpactExecute arbitrary PHP as web server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid WordPress account with Administrator-level privileges (or higher) and access to the CTX Feed Pro plugin's 'Feed Config' field, whose value is passed directly to PHP's eval(). The plugin (CTX Feed Pro / WooCommerce Product Feed Pro by Webappick) must be installed and active at version 7.6.12 or earlier. The decisive limiting factor is the Administrator prerequisite (PR:H): this is not exploitable by anonymous or low-privileged users, which sharply narrows realistic attackers to those who already hold or have stolen admin credentials, or to multi-admin environments where a lower-trust admin should not have code-execution rights. No user interaction beyond the attacker's own save action is needed (UI:N), and no non-default configuration is required. |
| Impact | This is a real but conditional risk. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2 High) shows network-reachable, low-complexity exploitation with full confidentiality/integrity/availability impact, but critically requires PR:H - Administrator-level access to WordPress. That high privilege requirement is the dominant mitigating factor and is why the score is capped at High rather than Critical: an attacker already holding admin can typically do significant damage through legitimate plugin/theme editing, so this flaw's marginal escalation is to arbitrary PHP RCE at the web-server process level. No EPSS score, CISA KEV listing, or public POC is present in the supplied data, so there is no signal of active or widespread exploitation (status: no public exploit identified at time of analysis). The CVSS attack vector (AV:N) and the description are consistent - exploitation is through an authenticated web interface. The main value here is for post-compromise persistence/code execution or for abuse of a rogue/secondary admin account, not for mass unauthenticated exploitation. Missing signals: EPSS and POC status are absent and should be treated as unknown rather than negative. |
| Exploit ScenarioDerived | An attacker who has obtained WordPress Administrator credentials (via phishing, credential reuse, or a separate privilege escalation) navigates to the CTX Feed Pro 'Feed Config' field and injects PHP code, which the plugin passes directly to eval(), yielding arbitrary PHP execution in the web-server context. No public exploit code is identified at time of analysis, and because the CVSS complexity is low (AC:L) and no user interaction is needed, the action succeeds immediately once admin access is held. This effectively converts admin-panel access into full server-side code execution. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Code injection in CTX Feed Pro (WooCommerce Product Feed Pro by Webappick) versions up to and including 7.6.12 allows an authenticated attacker with Administrator-level privileges to execute arbitrary PHP code on the server by supplying malicious input to the plugin's 'Feed Config' field, which is passed unsanitized to PHP's eval(). The vulnerability is not exploitable by anonymous or low-privileged users because it requires Administrator access, making the realistic threat model a stolen or malicious admin account or a multi-admin environment where a lower-trust admin should not have code-execution rights. No public exploit identified at time of analysis, and no confirmed active exploitation was reported.
RemediationAI
No exact fixed version is specified in the available references; check the vendor's product page (https://webappick.com/plugin/woocommerce-product-feed-pro/) and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/50aa4bff-60dd-469c-a8f0-be6dd2dfa91e?source=cve) for an updated release and upgrade CTX Feed Pro immediately to the latest version if one is available. Because the flaw requires Administrator privileges, the most effective compensating controls are to restrict and monitor administrative access: enforce least-privilege by reducing the number of Administrator accounts, enable strong unique passwords and multi-factor authentication for all admins, and audit admin account activity for unexpected changes to plugin settings. If the plugin is not essential, disable or remove it; if it must remain active and no patch is confirmed, consider using a web application firewall (WAF) to block requests that attempt to write PHP code into the 'Feed Config' field, and review server logs for suspicious eval-related errors or unauthorized admin logins. Note that WAF rules can be bypassed and may block legitimate feed configuration changes, so they are a temporary measure. There is no known workaround that fully removes the eval() exposure without modifying the plugin code, which is not recommended for production sites.
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 vulnerability is a CWE-94 (Improper Control of Generation of Code / Code Injection) flaw in the CTX Feed Pro WordPress plugin, where the 'Feed Config' field is not properly validated or sanitized before being passed directly to PHP's eval() function. eval() executes a string as PHP code, so any attacker-controlled value reaching it can run arbitrary server-side code with the privileges of the web server process. According to the CPE cpe:2.3:a:ctx:ctx_feed_pro:*:*:*:*:*:*:*:* the entire CTX Feed Pro product line is represented as affected, but the description narrows the vulnerable range to versions up to and including 7.6.12. The attack vector is network-accessible (AV:N), requires high privileges (PR:H) and no user interaction (UI:N), and results in high confidentiality, integrity, and availability impact (C:H/I:H/A:H) because code execution on the server can lead to data theft, site takeover, or defacement. WordPress plugins that expose administrative configuration fields are common targets for this class of bug when developer input validation is missing.
Know when Ctx Feed Pro 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:H/UI:N/S:U/C:H/I:H/A:H
Exploitation requires authenticated Administrator access so PR:H; the admin web interface is network-reachable (AV:N) with low complexity (AC:L) and eval() yields full C/I/A impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The CTX Feed Pro plugin for WordPress is vulnerable to Code Injection in all versions up to, and including, 7.6.12. This is due to insufficient input validation on the 'Feed Config' field which is passed directly to the eval() function. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute arbitrary PHP code on the server.
Executive ViewAI
A code-injection weakness in CTX Feed Pro (WooCommerce Product Feed Pro by Webappick), versions up to and including 7.6.12, lets anyone holding Administrator rights on a WordPress store execute arbitrary PHP code on the underlying web server. The practical risk is not anonymous attackers but the abuse of a stolen, shared, or over-privileged admin account - a single such account converts into full control of the e-commerce platform and anything it stores or connects to. With no vendor patch available, every site running an affected version remains exposed, and leadership should treat this as an open, unmitigated risk to customer data and revenue continuity.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict Administrator-role membership to the minimum necessary accounts and enforce MFA plus unique credentials on all of them; deploy WAF or virtual-patch rules that block PHP code sequences in the plugin's 'Feed Config' field; restrict wp-admin/wp-login.php by IP allowlist; set DISALLOW_FILE_EDIT and remove web-server write access to plugin directories; temporarily deactivate CTX Feed Pro where feed generation can tolerate an outage; enable file-integrity monitoring and review web server, PHP, and plugin logs for unexpected code or configuration changes; isolate the WordPress host so a code-execution event cannot reach adjacent internal systems.
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
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-91171
GHSA-m8mq-x2gc-8xcm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB