DodosMail dodosmail_header_file file include

dodosmail-dodosmailheader-file-include (43625) The risk level is classified as MediumMedium Risk


DodosMail could allow a remote attacker to include arbitrary files. A remote attacker could send a specially-crafted URL request to the dodosmail.php script using the dodosmail_header_file parameter to specify a malicious file from the local system, which could allow the attacker to obtain sensitive information or execute arbitrary code on the vulnerable Web server.

Note: In order to exploit this vulnerability to execute arbitrary code, the attacker would first be required to upload a malicious file or inject arbitrary commands into an existing file.


Base Score: 6.8
  Access Vector: Network
  Access Complexity: Medium
  Authentication: None
  Confidentiality Impact: Partial
  Integrity Impact: Partial
  Availability Impact: Partial
Temporal Score: 5.5
  Exploitability: Unproven
  Remediation Level: Unavailable
  Report Confidence: Uncorroborated


Gain Access


No remedy available as of September 1, 2014.


  • Dodo's Scripts Collection Web site: DodosMail.
  • BID-30112: DodosMail 'dodosmail.php' Local File Include Vulnerability
  • CVE-2008-3163: Directory traversal vulnerability in dodosmail.php in DodosMail 2.5 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the dodosmail_header_file parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
  • OSVDB ID: 47047: DodosMail dodosmail.php dodosmail_header_file Parameter Traversal Local File Inclusion

Platforms Affected:

  • Ying Zhang DodosMail 2.5


Jul 07, 2008

The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this

Return to the main page