Particle Soft Particle Links 1.2.2 index.php topic sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Particle Soft Particle Links 1.2.2. Impacted is an unknown function of the file index.php. Performing a manipulation of the argument topic results in sql injection. This vulnerability is reported as CVE-2006-2904. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in Particle Soft Particle Links 1.2.2. This affects an unknown functionality of the file index.php. The manipulation of the argument topic with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in index.php in Partial Links 1.2.2 allows remote attackers to execute arbitrary SQL commands via the topic parameter.
The weakness was disclosed 06/08/2006 by luny as confirmed posting (Bugtraq). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2006-2904 since 06/08/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (26955), SecurityFocus (BID 18342†) and Secunia (SA20491†). The entries VDB-30718, VDB-30716 and VDB-30715 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: 🔍
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
06/06/2006 🔍06/07/2006 🔍
06/08/2006 🔍
06/08/2006 🔍
06/08/2006 🔍
03/12/2015 🔍
09/16/2017 🔍
Sources
Advisory: securityfocus.com⛔Researcher: luny
Status: Confirmed
CVE: CVE-2006-2904 (🔍)
GCVE (CVE): GCVE-0-2006-2904
GCVE (VulDB): GCVE-100-30717
X-Force: 26955 - Particle Links index.php SQL injection
SecurityFocus: 18342 - Particle Links SQL Injection Vulnerability
Secunia: 20491 - Particle Links "username" Parameter Cross-Site Scripting, Less Critical
See also: 🔍
Entry
Created: 03/12/2015 14:25Updated: 09/16/2017 10:57
Changes: 03/12/2015 14:25 (54), 09/16/2017 10:57 (7)
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.