ClipBucket < 5.5.3-#182 Blind SQL Injection via Private Message Deletion Endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MacWarrior | clipbucket-v5 | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Macwarrior | Clipbucket-v5 |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.424% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oxygenz
Oxygenz clipbucket |
|
| CPEs | cpe:2.3:a:oxygenz:clipbucket:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Oxygenz
Oxygenz clipbucket |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Macwarrior
Macwarrior clipbucket-v5 |
|
| Vendors & Products |
Macwarrior
Macwarrior clipbucket-v5 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ClipBucket v5 through 5.5.3 contains a blind SQL injection vulnerability that allows authenticated users to extract arbitrary database contents by submitting the msg_id parameter as an array to bypass the clean_requests() sanitization function in ClipBucket.class.php. Attackers can pass unsanitized array elements through the deletion handler in private_message.php into cb_pm::delete_msg(), which interpolates the unescaped message ID directly into a SQL query string, enabling time-based blind SQL injection to retrieve all user credential hashes and email addresses. | ClipBucket v5 before 5.5.3-#182 contains a blind SQL injection vulnerability that allows authenticated users to extract arbitrary database contents by submitting the msg_id parameter as an array to bypass the clean_requests() sanitization function in ClipBucket.class.php. Attackers can pass unsanitized array elements through the deletion handler in private_message.php into cb_pm::delete_msg(), which interpolates the unescaped message ID directly into a SQL query string, enabling time-based blind SQL injection to retrieve all user credential hashes and email addresses. |
| Title | ClipBucket 5.5.3 Blind SQL Injection via Private Message Deletion Endpoint | ClipBucket < 5.5.3-#182 Blind SQL Injection via Private Message Deletion Endpoint |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ClipBucket v5 through 5.5.3 contains a blind SQL injection vulnerability that allows authenticated users to extract arbitrary database contents by submitting the msg_id parameter as an array to bypass the clean_requests() sanitization function in ClipBucket.class.php. Attackers can pass unsanitized array elements through the deletion handler in private_message.php into cb_pm::delete_msg(), which interpolates the unescaped message ID directly into a SQL query string, enabling time-based blind SQL injection to retrieve all user credential hashes and email addresses. | |
| Title | ClipBucket 5.5.3 Blind SQL Injection via Private Message Deletion Endpoint | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|