InterWorx NodeWorx siteworx.php PATH_INFO cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in InterWorx NodeWorx and classified as problematic. This affects an unknown part of the file siteworx.php. Performing a manipulation of the argument PATH_INFO results in cross site scripting. This vulnerability is known as CVE-2007-4588. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as problematic has been found in InterWorx NodeWorx (Server Management Software) (the affected version unknown). This affects an unknown part of the file siteworx.php. The manipulation of the argument PATH_INFO with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity.
The weakness was published 08/30/2007 (Website). The advisory is shared at interworx.com. This vulnerability is uniquely identified as CVE-2007-4588 since 08/28/2007. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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:siteworx.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 (36746†) and Secunia (SA26586†). Similar entries 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-85725
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: 36746 - InterWorx-CP NodeWorx siteworx.php PATH_INFO Parameter XSS
See also: 🔍
Entry
Created: 05/08/2016 22:01Updated: 08/11/2022 13:10
Changes: 05/08/2016 22:01 (55), 01/06/2019 10:29 (5), 08/11/2022 13:10 (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.