CVE-2026-103474

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

GHSA-hfh8-jhpw-h99w ↗EUVD-2026-90205 ↗

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
ETK-2026-159, permanent identifier
20d 11h 03msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h30m
0
+2h
+6h
+8h
+10h
+12h

description

yii2-starter-kit through 4.2.0 does not adequately restrict file types in backend storage uploads. An authenticated user with the manager role may upload server-executable PHP content and have it run if the storage directory is web accessible and configured to execute PHP.

mitigation

Prevent execution of scripts from the upload storage directory and restrict manager-role access to trusted users. Apply an upstream release containing a file-type validation fix when one is identified.

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, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.39%31st percentile
agent run time
12m
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

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-09-30 17:22Z
    ghsa: trigger signal, started the run
  2. 2026-09-30 17:22Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-159",
  "cve_id": "CVE-2026-103474",
  "display_id": "CVE-2026-103474",
  "ghsa_id": "GHSA-hfh8-jhpw-h99w",
  "euvd_id": "EUVD-2026-90205",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Insufficient file-type validation in yii2-starter-kit",
  "summary": "yii2-starter-kit through 4.2.0 does not adequately restrict file types in backend storage uploads. An authenticated user with the manager role may upload server-executable PHP content and have it run if the storage directory is web accessible and configured to execute PHP.",
  "mitigation": "Prevent execution of scripts from the upload storage directory and restrict manager-role access to trusted users. Apply an upstream release containing a file-type validation fix when one is identified.",
  "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": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0039,
  "epss_percentile": 0.3149,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.050466233333333,
  "t0_at": "2026-09-30T17:22:41.048000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T17:22:41.048000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T17:22:41.048000+00:00",
      "url": "https://github.com/advisories/GHSA-hfh8-jhpw-h99w"
    }
  }
}

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

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.