WordPress security by component
canvasio3D Light
Plugin description
canvasio3D Light is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Dec 09, 2024; the highest published CVSS base score is 9.9.
Plugin slug:
canvasio3d-lightLatest vulnerability
CVE-2023-48776: canvasio3D Light: A security weakness
canvasio3D Light is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Dec 09, 2024 |
CVE-2023-48776
canvasio3D Light: A security weakness
canvasio3D Light is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.4
NVDPending
|
| May 14, 2024 |
CVE-2024-34411
canvasio3D Light: Dangerous file upload
canvasio3D Light is affected by dangerous file upload. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can place attacker-controlled executable content on the server and may lead to full site compromise. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE9.9
NVDPending
|
| Oct 18, 2023 |
CVE-2023-45062
Canvasio3D Light: Cross-site scripting
Canvasio3D Light is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE7.1
NVD6.1
|