Security readout for executives and security teams
Plain-English summary
This is an old PHP iCalendar flaw where a remote user could manipulate a language cookie to make the application load local files. The source says this may allow local file inclusion and execution. Treat exposed legacy PHP iCalendar deployments as business-relevant risk until verified or retired.
Executive priority
Prioritize verification if PHP iCalendar is exposed to the internet. This is a legacy application issue with public exploit references and potentially serious server impact, but urgency depends on whether affected software still exists in the environment.
Technical view
CVE-2008-5968 affects PHP iCalendar 2.24 and earlier in print.php. The vulnerable input is cookie_language within a phpicalendar_* cookie using directory traversal. Public references describe local file inclusion with possible execution. No CVSS, CWE, or vendor remediation details are present in the provided bundle.
Likely exposure
Exposure is likely limited to organizations still running PHP iCalendar 2.24 or earlier with print.php reachable, especially on internet-facing legacy PHP hosting. The bundle does not identify affected CPEs or broader products.
Exploitation context
The source bundle includes an Exploit-DB reference, so public exploit information exists. CISA KEV status is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
Evidence is sparse: the CVE description identifies the vulnerable file, parameter, cookie context, and affected version range, but omits CVSS and patch details. Avoid assuming active exploitation or specific fixed versions from this bundle alone.
Mitigation direction
- Inventory internet-facing PHP iCalendar instances and identify versions.
- Retire unused PHP iCalendar deployments, especially legacy public installations.
- Restrict access to PHP iCalendar until remediation is confirmed.
- Check PHP iCalendar or vendor guidance for fixed releases or supported migration paths.
- Review web server hardening for local file include impact reduction.
Validation and detection
- Search asset inventory for PHP iCalendar deployments.
- Confirm whether any instance is version 2.24 or earlier.
- Verify whether print.php is reachable from untrusted networks.
- Review web logs for suspicious phpicalendar_* cookie activity.
- Document compensating controls for any instance that cannot be removed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2008-5968 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
- phpicalendar-print-file-include(48322)CVE reference · vdb-entry, x_refsource_XF
- 6519CVE reference · exploit, x_refsource_EXPLOIT-DB
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.