phpJobScheduler 3.0 firepjs.php installed_config_file file inclusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.97 |
Summary
A vulnerability classified as critical was found in phpJobScheduler 3.0. The affected element is an unknown function of the file firepjs.php. Executing a manipulation of the argument installed_config_file can lead to file inclusion. This vulnerability is tracked as CVE-2006-5929. No exploit exists.
Details
A vulnerability classified as critical was found in phpJobScheduler 3.0. This vulnerability affects an unknown function of the file firepjs.php. The manipulation of the argument installed_config_file 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. CVE summarizes:
PHP remote file inclusion vulnerability in firepjs.php in Phpjobscheduler 3.0 allows remote attackers to execute arbitrary PHP code via a URL in the installed_config_file parameter. NOTE: the provenance of this information is unknown; details are obtained from third party sources.
The weakness was disclosed 11/15/2006 (Website). The advisory is shared for download at secunia.com. This vulnerability was named CVE-2006-5929 since 11/15/2006. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
By approaching the search of inurl:firepjs.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 vulnerability database at Secunia (SA22855†). The entries VDB-33291, VDB-84839, VDB-84840 and VDB-84841 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/13/2006 🔍11/15/2006 🔍
11/15/2006 🔍
11/15/2006 🔍
03/12/2015 🔍
04/27/2026 🔍
Sources
Advisory: secunia.com⛔Status: Not defined
CVE: CVE-2006-5929 (🔍)
GCVE (CVE): GCVE-0-2006-5929
GCVE (VulDB): GCVE-100-33292
Secunia: 22855 - phpJobScheduler "installed_config_file" File Inclusion Vulnerabilities, Highly Critical
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 04/27/2026 16:19
Changes: 03/12/2015 22:21 (44), 08/08/2018 07:08 (7), 04/27/2026 16:19 (18)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.