| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in InterWorx NodeWorx. It has been classified as problematic. The impacted element is an unknown function of the file updates.php. This manipulation of the argument PATH_INFO causes cross site scripting. This vulnerability is handled as CVE-2007-4588. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in InterWorx NodeWorx (Server Management Software) (unknown version). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the file updates.php. The manipulation of the argument PATH_INFO with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity.
The weakness was released 08/30/2007 (Website). The advisory is shared at interworx.com. This vulnerability is known as CVE-2007-4588 since 08/28/2007. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
By approaching the search of inurl:updates.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 (36297), SecurityFocus (BID 25451†), OSVDB (36764†) and Secunia (SA26586†). Entries connected to this vulnerability are available at VDB-38559, VDB-38558, VDB-85720 and VDB-85721. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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: 🔍
Timeline
08/27/2007 🔍08/28/2007 🔍
08/28/2007 🔍
08/30/2007 🔍
08/30/2007 🔍
08/30/2007 🔍
05/08/2016 🔍
08/11/2022 🔍
Sources
Advisory: interworx.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2007-4588 (🔍)
GCVE (CVE): GCVE-0-2007-4588
GCVE (VulDB): GCVE-100-85741
X-Force: 36297
SecurityFocus: 25451 - InterWorx-CP SiteWorx and NodeWorx Multiple Cross-Site Scripting Vulnerabilities
Secunia: 26586 - InterWorx-CP Multiple Cross-Site Scripting, Less Critical
OSVDB: 36764 - InterWorx-CP NodeWorx updates.php PATH_INFO Parameter XSS
See also: 🔍
Entry
Created: 05/08/2016 22:02Updated: 08/11/2022 14:37
Changes: 05/08/2016 22:02 (56), 01/06/2019 10:17 (4), 08/11/2022 14:37 (3)
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.