A remote PHP code execution vulnerability exists in InstantCMS version 1.6 and earlier due to unsafe use of eval() within the search view handler. Specifically, user-supplied input passed via the look parameter is concatenated into a PHP expression and executed without proper sanitation. A remote attacker can exploit this flaw by sending a crafted HTTP GET request with a base64-encoded payload in the Cmd header, resulting in arbitrary PHP code execution within the context of the web server.
Security readout for executives and security teams
Plain-English summary
InstantCMS 1.6 and earlier can let an unauthenticated remote attacker run PHP code on the server. That can lead to full compromise of the website and hosted data. Treat any exposed legacy InstantCMS deployment as urgent until proven patched or removed.
Executive priority
Handle as a high-urgency legacy web application risk. Public exploit material and unauthenticated remote code execution make exposed systems unacceptable for normal operation without confirmed remediation or isolation.
Technical view
The vulnerability is unsafe eval() handling in the InstantCMS search view. User-controlled input in the look parameter is incorporated into a PHP expression without adequate sanitization, enabling arbitrary PHP execution in the web server context. The CVSS 4.0 score is 9.3 critical.
Likely exposure
Exposure is most likely on internet-facing InstantCMS sites running version 1.6 or earlier. The structured affected-version data is incomplete, so inventory should verify actual deployed versions, search functionality, and public reachability.
Exploitation context
The provided sources include public exploit references, including Rapid7 Metasploit, Exploit-DB, and Packet Storm. The CVE is not marked KEV, and the bundle provides no evidence of active exploitation in the wild.
Researcher notes
Evidence supports RCE via unsafe eval() in the search handler, but affected-version metadata is weak and no patch details are included. Avoid assuming broader product impact beyond InstantCMS 1.6 and earlier without vendor confirmation.
Mitigation direction
Identify all InstantCMS deployments and prioritize version 1.6 or earlier.
Check InstantCMS or vendor guidance for fixed versions or official workarounds.
Restrict public access to vulnerable InstantCMS search functionality where feasible.
Retire or isolate unsupported legacy InstantCMS instances.
Review web server logs for suspicious requests against InstantCMS search routes.
Validation and detection
Confirm whether InstantCMS is present in external and internal asset inventory.
Verify deployed InstantCMS versions against 1.6 and earlier.
Check whether affected search views are reachable without authentication.
Review logs for anomalous search requests and unexpected PHP execution indicators.
Confirm remediation through version review and controlled application testing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-95 · source CWE mapping
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.