ILC Thickbox <= 1.0 - Settings update via CSRF
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Unknown | ILC Thickbox | affected |
|
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.201% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Elliot
Elliot ilc Thickbox |
|
| CPEs | cpe:2.3:a:elliot:ilc_thickbox:*:*:*:*:*:wordpress:*:* | |
| Vendors & Products |
Elliot
Elliot ilc Thickbox |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ilc Thickbox
Ilc Thickbox ilc Thickbox |
|
| Weaknesses | CWE-352 | |
| CPEs | cpe:2.3:a:ilc_thickbox:ilc_thickbox:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Ilc Thickbox
Ilc Thickbox ilc Thickbox |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The ILC Thickbox WordPress plugin through 1.0 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack | |
| Title | ILC Thickbox <= 1.0 - Settings update via CSRF | |
| References |
|