← Back to results
Vulnerability record · public intelligence
CVE-2024-30248
HIGH

Piccolo Admin's raw SVG loading may lead to complete data compromise from admin page

Published Apr 2, 2024 · Updated Oct 23, 2026 · Also known as GHSA-pmww-v6c9-7p83, PYSEC-2026-1780

Severity · CVSSHIGH · 7.7
Known exploitationNot listed
EPSS / likelihood0.49%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

Piccolo Admin's raw SVG loading may lead to complete data compromise from admin page

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Piccolo's admin panel provides the ability to upload media files and view them within the admin panel. If SVG is an allowed file type for upload; the default; an attacker can upload an SVG which when loaded under certain contexts allows for arbitrary access to the admin page. This access allows the following actions for example: - The ability for an attacker to gain access to all data stored within the admin page - The ability for an attacker to make any action within the admin page such as creating, modifying or deleting table records As the SVG is executed from the context of an authenticated admin session, any actions they may be able to make can be made by the attacker. N.b. The relevant session cookies are inaccessible from JavaScript due to httponly being set so all exploits must be present within the SVG file

Potential impact

What kind of vulnerability is it? Who is impacted? All applications with the following conditions present are affected: - An enabled admin panel - A model which features media upload that allows for SVG files Further, if the site is behind a proxy of sorts it must not set the relevant security headers.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
MEDIUM
Confidence
10%
Aliases
GHSA-pmww-v6c9-7p83, PYSEC-2026-1780

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗

Record history

Published Apr 2, 2024 · Last refreshed Oct 23, 2026