| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Softbiz FAQ Script. This issue affects some unknown processing of the file add_comment.php. Such manipulation of the argument ID leads to sql injection. This vulnerability is uniquely identified as CVE-2005-3938. The attack can be launched remotely. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, has been found in Softbiz FAQ Script (affected version unknown). Affected by this issue is an unknown functionality of the file add_comment.php. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 11/28/2005 by r0t (Website). The advisory is shared for download at pridels.blogspot.com. This vulnerability is handled as CVE-2005-3938. The attack may be launched remotely. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.
The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:add_comment.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 (23296), Exploit-DB (26677), SecurityFocus (BID 15653†), OSVDB (21261†) and Secunia (SA17809†). The entries VDB-27217, VDB-83249, VDB-83250 and VDB-83251 are pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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: 🔍
0-Day Time: 🔍
Timeline
11/28/2005 🔍11/30/2005 🔍
11/30/2005 🔍
12/01/2005 🔍
05/04/2016 🔍
11/28/2025 🔍
Sources
Advisory: pridels.blogspot.comResearcher: r0t
Status: Not defined
CVE: CVE-2005-3938 (🔍)
GCVE (CVE): GCVE-0-2005-3938
GCVE (VulDB): GCVE-100-83252
X-Force: 23296
SecurityFocus: 15653 - Softbiz FAQ Multiple SQL Injection Vulnerabilities
Secunia: 17809
OSVDB: 21261 - Softbiz FAQ Script add_comment.php id Parameter SQL Injection
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/04/2016 10:23Updated: 11/28/2025 08:00
Changes: 05/04/2016 10:23 (41), 11/09/2018 09:15 (7), 07/28/2022 07:33 (3), 07/28/2022 07:39 (7), 11/28/2025 08:00 (25)
Complete: 🔍
Cache ID: 216:579:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.