| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in comus 2.0 Final. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the file accept.php. This manipulation of the argument DOCUMENT_ROOT causes file inclusion. This vulnerability is handled as CVE-2007-2287. Additionally, an exploit exists.
Details
A vulnerability was found in comus 2.0 Final. It has been declared as critical. Affected by this vulnerability is an unknown function of the file accept.php. The manipulation of the argument DOCUMENT_ROOT with an unknown input leads to a file inclusion vulnerability. The CWE definition for the vulnerability is CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
PHP remote file inclusion vulnerability in accept.php in comus 2.0 Final allows remote attackers to execute arbitrary PHP code via a URL in the DOCUMENT_ROOT parameter.
The weakness was released 05/03/2007 by Alijsb (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2007-2287 since 04/26/2007. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
After before and not just, there has been an exploit disclosed. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:accept.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (33870), Exploit-DB (29907), SecurityFocus (BID 23661†) and OSVDB (34168†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: File inclusionCWE: CWE-73
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
04/25/2007 🔍04/26/2007 🔍
04/26/2007 🔍
05/03/2007 🔍
05/03/2007 🔍
05/03/2007 🔍
03/13/2015 🔍
07/13/2025 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Alijsb
Status: Not defined
CVE: CVE-2007-2287 (🔍)
GCVE (CVE): GCVE-0-2007-2287
GCVE (VulDB): GCVE-100-36421
X-Force: 33870 - Comus accept.php file include
SecurityFocus: 23661 - Comus Accept.PHP Remote File Include Vulnerability
OSVDB: 34168 - comus accept.php DOCUMENT_ROOT Parameter Remote File Inclusion
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/13/2015 14:56Updated: 07/13/2025 03:09
Changes: 03/13/2015 14:56 (52), 08/30/2018 08:36 (7), 07/13/2025 03:09 (24)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.