10up Safe SVG for WordPress
Approved changes feed: RSS · Atom
cpe:2.3:a:10up:safe_svg:-:*:*:*:*:wordpress:*:*
part: a version: - update: *
| Vendor | 10Up (881e212c-90bc-5d75-a450-4d45d1038060) |
|---|---|
| Product | Safe Svg (db7bd3f9-1cb6-59e5-a952-61b7186c0f7d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/10up/safe-svg |
purl2cpe | 2026-06-01 10:16:44.778379 |
pkg:github/wp-plugins/safe-svg |
purl2cpe | 2026-06-01 10:16:44.778380 |
pkg:github/wpplugins/safe-svg |
purl2cpe | 2026-06-01 10:16:44.778381 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-8378 |
vulnerable | 2026-06-08 07:00:24.435861 |
Safe SVG < 2.2.6 - Author+ SVG Sanitisation Bypass
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.
Published: 2024-11-07T15:07:36.788Z
Updated: 2024-11-07T19:53:59.721Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.