CVE-2026-10026

waiting for further signalsZero needs more public information before it can validate it.

GHSA-m8mq-x2gc-8xcm ↗EUVD-2026-91171 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
CTX Feed Pro <= 7.6.12
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-422, permanent identifier
18d 05h 44msince last run
1h 01mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+26h27m
0
+2h
+4h
+6h
+8h
+10h

description

CTX Feed Pro for WordPress through version 7.6.12 does not safely validate a feed configuration setting before evaluating it as PHP. An attacker with an Administrator-level WordPress account can use this flaw to run PHP code on the server.

mitigation

Disable CTX Feed Pro where it is not required, and restrict Administrator access to trusted users until the vendor provides and you deploy a confirmed fix. Monitor for an updated release, as no fixed version is recorded.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.32%23rd percentile
agent run time
1h 01m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 04:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-02 04:27Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-10026

{
  "etk_id": "ETK-2026-422",
  "cve_id": "CVE-2026-10026",
  "display_id": "CVE-2026-10026",
  "ghsa_id": "GHSA-m8mq-x2gc-8xcm",
  "euvd_id": "EUVD-2026-91171",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Administrator-authenticated code injection in CTX Feed Pro",
  "summary": "CTX Feed Pro for WordPress through version 7.6.12 does not safely validate a feed configuration setting before evaluating it as PHP. An attacker with an Administrator-level WordPress account can use this flaw to run PHP code on the server.",
  "mitigation": "Disable CTX Feed Pro where it is not required, and restrict Administrator access to trusted users until the vendor provides and you deploy a confirmed fix. Monitor for an updated release, as no fixed version is recorded.",
  "vendor": "CTX",
  "product": "CTX Feed Pro",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 7.6.12"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "CTX Feed Pro",
      "purl": null
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0032,
  "epss_percentile": 0.2332,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 61.35058643333333,
  "t0_at": "2026-10-02T04:27:11.832000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T04:27:11.832000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T04:27:11.832000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-10026"
    }
  }
}

published 2026-10-03 05:52Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.