# CVE-2026-10026: CTX Feed Pro <= 7.6.12 - Authenticated (Administrator+) Remote Code Execution

> Administrators can execute arbitrary PHP code via the Feed Config field due to unsafe eval usage in CTX Feed Pro.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-m8mq-x2gc-8xcm

## What is CVE-2026-10026?

CVE-2026-10026 is a high-severity code injection vulnerability in CTX Feed Pro, published on 2 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-10026?


## How do I fix CVE-2026-10026?

No fix has been published for CVE-2026-10026 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10026 being exploited?

There is no known exploitation of CVE-2026-10026 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10026 and fix it if it is affected.

What it is: CVE-2026-10026 is a high-severity code injection vulnerability in CTX Feed Pro, published on 2 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10026 in the wild and no public exploit code.

Affected product: CTX Feed Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10026/ (Markdown: https://insights.sbomify.com/CVE-2026-10026/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10026
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10026
- OSV: https://osv.dev/vulnerability/CVE-2026-10026

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10026/
Summaries are generated and may contain mistakes; the official description above is the record.