Safe SVG: A security weakness
Safe SVG 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.
- Component
- Safe SVG
- Plugin slug
safe-svg- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Nov 07, 2024
- Weakness
- NVD-CWE-noinfo
This CVE was published Nov 07, 2024 and is one of 4 known issues for this plugin.
Update, patch or deactivate.
Update Safe SVG to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Safe SVG WordPress plugin before 2.2.6 has its sanitisation code is only running for paths that call wp_handle_upload, but not for example for code that uses wp_handle_sideload which is often used to upload attachments via raw POST data.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N