Analyst readout for executives and security teams
Plain-English summary
CVE-2003-1402 is a legacy Kietu PHP issue where a web request could make the application include remote PHP code. If an exposed Kietu 2.0 or 2.3 site still exists, compromise could mean server-side code execution. The source bundle does not identify a patch.
Executive priority
Prioritize if any legacy Kietu instance is internet-facing. The vulnerability class can lead to server compromise, but urgency depends on confirming the old software is still deployed.
Technical view
The vulnerability is a PHP remote file inclusion issue in Kietu hit.php. Sources identify the url_hit parameter as the affected input and state that remote attackers may execute arbitrary PHP code. The record says this is distinct from CVE-2006-5015.
Likely exposure
Exposure appears limited to legacy PHP deployments running Kietu 2.0 or 2.3 with hit.php reachable. The provided CVE metadata does not include CPEs, vendors, or broader affected-product data, so inventory confirmation is necessary.
Exploitation context
The bundle supports remote arbitrary PHP code execution as the impact. It does not support claims of active exploitation: KEV is false, and no cited source in the bundle confirms current exploitation activity.
Researcher notes
Evidence is sparse and old. The record identifies Kietu 2.0 and 2.3, hit.php, and url_hit, but provides no CVSS, CWE, CPE, patch version, or current exploit confirmation in the supplied bundle.
Mitigation direction
- Identify whether Kietu 2.0 or 2.3 exists anywhere in production or archives.
- Check vendor or historical advisory guidance for any official fix or replacement.
- Remove or retire exposed Kietu instances that cannot be verified as fixed.
- Restrict public access to hit.php while remediation decisions are made.
- Review web server logs for suspicious requests targeting hit.php and url_hit.
Validation and detection
- Search asset inventories and web roots for Kietu deployments and hit.php.
- Confirm deployed Kietu version numbers where the application is found.
- Verify whether hit.php is internet-accessible on any active host.
- Check logs for historical requests containing the url_hit parameter.
- Document whether any compensating controls block access to the affected script.
Public sources used
Based on public source material and reviewed before publication.
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.
CVE-2003-1402 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- kietu-hit-file-include(11341)CVE reference · vdb-entry, x_refsource_XF
- 3777CVE reference · vdb-entry, x_refsource_OSVDB
- 6863CVE reference · vdb-entry, x_refsource_BID
- 20030215 Kietu ( PHP )CVE reference · mailing-list, x_refsource_VULNWATCH
- 10754CVE reference · third-party-advisory, x_refsource_SECUNIA
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.