Skip to main content

Yii2 Starter Kit EUVDEUVD-2026-90206

| CVE-2026-103475 CRITICAL
Active Debug Code (CWE-489)
2026-09-30 VulnCheck GHSA-92vv-q57x-j4vj
9.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Discover exposed debug/Gii endpoints
  2. Delivery
    Send unauthenticated HTTP request to debug module
  3. Exploit
    Read session cookies and DB queries
  4. Execution
    Invoke Gii to write PHP into app directory
  5. Impact
    Execute planted PHP for code execution

Vulnerability Assessment

Weakness
CWE
Exploitation Conditions

Exploitable only when a yii2-starter-kit application (through 4.2.0) is deployed with its development configuration active and network-reachable, because that profile sets the debug and Gii modules' allowedIPs to ['*'] (see common/config/web.php line 21). Given that, no authentication or user interaction is required - any remote client can hit the debug endpoint to read session cookies and database queries, and the Gii endpoint to generate and write PHP into the application directory. The primary limiting factor is deployment posture: a correctly hardened production configuration restricts allowedIPs (typically to localhost), so internet exposure requires an operator shipping the dev/staging profile publicly.

Impact

The vendor CVSS 4.0 score of 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H) reflects a genuinely dangerous outcome: unauthenticated network attackers reach the Yii debug module (leaking session cookies and executed database queries → VC:H) and the Gii code generator (writing attacker-controlled PHP files into the application directory → VI:H, effectively a path to remote code execution). SSVC-wise the technical impact is high and the flaw is trivially automatable via simple HTTP requests. However, the single most important mitigating signal is buried in the description: this exposure exists in the DEFAULT DEVELOPMENT configuration (allowedIPs set to ['*'] in common/config/web.php), not a hardened production build. Real-world risk therefore hinges entirely on whether an operator deployed the development/staging profile to an internet-reachable host - a real and common misconfiguration, but not the framework's intended production posture. No EPSS score, no CISA KEV listing, and no public exploit code were supplied, so there is no evidence of active exploitation; the 9.3 is a worst-case rating rather than a confirmed widespread-exploitation priority. This is best characterized as a high-impact, low-prevalence issue whose true exposure depends on deployment discipline.

Exploit ScenarioDerived

An operator deploys a yii2-starter-kit application (≤4.2.0) to an internet-facing server while retaining the development configuration. An unauthenticated attacker requests the debug endpoint to harvest session cookies and database query contents, then invokes the Gii generator endpoint to write a malicious PHP file into the webroot, which is subsequently executed to achieve code execution. No public proof-of-concept was referenced, but exploitation requires only ordinary HTTP requests (AV:N/AC:L/PR:N).

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 30, 2026

Unauthenticated remote attackers who can reach a yii2-starter-kit deployment (through version 4.2.0) running with its default development configuration can read sensitive runtime data and write arbitrary PHP files. The dev profile sets the Yii debug and Gii modules' allowedIPs to ['*'] in common/config/web.php, so the debug endpoint leaks session cookies and executed database queries (C:H) while the Gii code generator can be abused to create attacker-controlled PHP in the application directory (I:H), a practical path to remote code execution. Exploitation requires the application to be network-exposed while still running the development/staging configuration; a properly hardened production deployment restricts allowedIPs (typically to localhost). No public exploit identified at time of analysis, and the issue is not in CISA KEV; EPSS data was not supplied.

RemediationAI

No vendor-released patch version is identified in the available data; the tracked issue at https://github.com/yii-starter-kit/yii2-starter-kit/issues/797 has not been confirmed as fixed in a tagged release, so treat this as a configuration-hardening problem rather than waiting on an upstream tag. The immediate and most reliable action is to stop running the development profile on any network-reachable host: deploy with the production configuration so the debug and gii modules are not registered, or, if they must remain, edit common/config/web.php to replace allowedIPs => ['*'] with an explicit allowlist of trusted management IPs (localhost/127.0.0.1 and the CI or admin ranges) - the trade-off is that developers lose remote access to the debugger and code generator and must tunnel or work locally, which is the intended posture. As a compensating control for systems that cannot be reconfigured quickly, block the debug and Gii route prefixes at the reverse proxy or web server (deny the default Yii debug routes such as /debug/* and the Gii entry point from all non-administrative source addresses) and rotate any application session cookies and database credentials that may have been leaked through the debug panel before restricting access. Note that disabling only the Gii endpoint still leaves the debug panel exposing session cookies and SQL logs, and vice versa; both must be closed. After remediation, verify by requesting the debug and Gii paths from an external address and confirming a 403/404 rather than a rendered panel.

Affected VersionsENISA

yii2-starter-kit 0 ≤4.2.0

Affected Packages

euvd yii2_starter_kit no fix

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

yii2-starter-kit is an open-source Yii2 application template (CPE cpe:2.3:a:yii2-starter-kit:yii2-starter-kit:*:*:*:*:*:*:*:*), and the flaw is classified as CWE-489, Leftover Debug Code. The Yii debugging toolbar/log module and the Gii CRUD/code generator are development-only components that normally gate access via an allowedIPs allowlist; the shipped default development configuration sets that allowlist to ['*'] (per the referenced blob at common/config/web.php line 21), effectively removing the access control rather than being a memory-safety or injection defect. Because these modules are plain HTTP endpoints reachable over the application's web port, any client - no credentials, no interaction (CVSS 4.0 AV:N/AC:L/AT:N/PR:N/UI:N; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N) - can query the debug panel for the session cookie jar and the logged SQL statements, and can drive the Gii generator to emit PHP source into the app tree. Impact is bounded to confidentiality and integrity (VC:H/VI:H, VA:N in the 4.0 vector; S:U in the 3.1 assessment), since the debugger itself is not a denial-of-service surface. Nothing in the underlying Yii framework is broken; the exposure is entirely a configuration-posture problem introduced by shipping permissive dev defaults.

Know when PHP 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

Vendor (VulnCheck) PRIMARY 9.3 CRITICAL
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
vuln.today AI 9.1 CRITICAL

Unauthenticated network HTTP access with no interaction (AV:N/AC:L/PR:N/UI:N); debug leak gives C:H and Gii PHP-file write gives I:H; no direct availability loss (A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

yii2-starter-kit through 4.2.0 exposes the Yii debug and Gii modules to all IP addresses by setting allowedIPs to ['*'] in its default development configuration. Unauthenticated remote attackers can access the debug endpoint to read sensitive data including session cookies and database queries, or access the Gii endpoint to generate and write PHP files into the application directory.

Executive ViewAI

Why It Matters

The yii2-starter-kit application framework (through version 4.2.0) contains a critical flaw that only manifests when a deployment is left running its default development configuration while reachable from the network. In that state an outside party can read live session cookies and executed database queries and can write arbitrary PHP into the application directory, which is a direct path to full server compromise. Any business unit running this starter kit in a lab, staging, or pilot environment that is internet-exposed should treat its data and availability as at risk until the configuration is corrected or a vendor patch is released.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict the debug and Gii modules' allowedIPs in common/config/web.php away from the default wildcard (typically to localhost), disable the Gii generator and Yii debug module outside development, remove development/staging-configured instances from direct internet exposure via VPN or IP allowlisting, block the corresponding endpoint paths at the WAF or reverse proxy, and monitor for unauthorized PHP file creation in the application directory.

Threat Intelligence Overview

EPSS Score
0.7%
Top 50% exploitable
Prevalence
Low
Yii2 project scaffolding template, niche developer tool, limited production footprint
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.7%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy