CVE-2026-103475

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

GHSA-92vv-q57x-j4vj ↗EUVD-2026-90206 ↗

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.
yii2-starter-kit <= 4.2.0
CWE-489 Active Debug Code
ETK-2026-136, permanent identifier
22h 36msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+472h59m
0
+2h
+4h
+6h
+8h
+10h

description

yii2-starter-kit versions through 4.2.0 can make the Yii Debug and Gii modules reachable from any IP address through its default development configuration. When that configuration is deployed and network-accessible, unauthenticated attackers may read diagnostic information or create PHP files in the application directory.

mitigation

Do not deploy the development configuration to reachable environments; disable the Debug and Gii modules where they are not needed. Replace the wildcard allowedIPs setting with a restricted administrative IP allowlist.

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.40%32nd percentile
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 17:22Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-09-30 17:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-136",
  "cve_id": "CVE-2026-103475",
  "display_id": "CVE-2026-103475",
  "ghsa_id": "GHSA-92vv-q57x-j4vj",
  "euvd_id": "EUVD-2026-90206",
  "status": "triaged_in_scope",
  "anchor_state": "anchored",
  "title": "Exposed development modules in yii2-starter-kit",
  "summary": "yii2-starter-kit versions through 4.2.0 can make the Yii Debug and Gii modules reachable from any IP address through its default development configuration. When that configuration is deployed and network-accessible, unauthenticated attackers may read diagnostic information or create PHP files in the application directory.",
  "mitigation": "Do not deploy the development configuration to reachable environments; disable the Debug and Gii modules where they are not needed. Replace the wildcard `allowedIPs` setting with a restricted administrative IP allowlist.",
  "vendor": "yii2-starter-kit",
  "product": "yii2-starter-kit",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "yii2-starter-kit",
      "purl": null
    }
  ],
  "cwes": [
    489
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.004,
  "epss_percentile": 0.3246,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.088041366666666,
  "t0_at": "2026-09-30T17:22:41.761000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T17:22:41.761000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T17:22:41.761000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103475"
    }
  }
}

published 2026-09-30 18:11Z
last change 2026-10-21 08:40Z

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.