How severe is GHSA-pmww-v6c9-7p83?

GHSA-pmww-v6c9-7p83 has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-pmww-v6c9-7p83?

GHSA-pmww-v6c9-7p83 affects the following packages: piccolo-admin (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-pmww-v6c9-7p83?

Update piccolo-admin to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pmww-v6c9-7p83 is resolved across your whole dependency graph.

How do I detect GHSA-pmww-v6c9-7p83 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for piccolo-admin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-pmww-v6c9-7p83 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pmww-v6c9-7p83?

O3 pinpoints whether GHSA-pmww-v6c9-7p83 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-pmww-v6c9-7p83 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pmww-v6c9-7p83 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pmww-v6c9-7p83?

GHSA-pmww-v6c9-7p83 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pmww-v6c9-7p83?

GHSA-pmww-v6c9-7p83 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-pmww-v6c9-7p83 published, and has it been updated?

GHSA-pmww-v6c9-7p83 was published on April 1, 2024 and was last updated on April 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-pmww-v6c9-7p83

HIGH

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

Also known asCVE-2024-30248

Published

Apr 1, 2024

Updated

Apr 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk39th percentile+0.37%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍piccolo-admin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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

PoC

Complete instructions, including specific configuration details, to reproduce the vulnerability.

Currently, this requires the ability for a user to have access to an administrators account in order to upload the malicious file for simplicity sake. I can however imagine situations where general end users have the ability to upload files which can later be managed via the admin page.

See the following repository: Piccolo XSS

Clone the repo
Run all migrations & create an admin user
Run app.py as a FastAPI application
Login to the admin page
Create a new task and upload the following file to see basic execution: payloads/basic_xss.svg
Click the SVG to view it inline
Click "Open image in new tab"
Observe the XSS triggering

Fig 1: An example XSS payload executing

Extended PoC

This repo also includes an extended PoC which sends the Task table to an attacker controlled server.

Run exhil_server.py as a FastAPI application
Upload the following payload: payloads/exhil.svg
Open the SVG in a new tab and observe the data being sent to the attacker controlled server

Fig 2: An example screenshot from the attacker controlled server showing incoming data Example data sent to attacker server

Further, the repo includes a list of routes the admin panel exposes which could be used to automate table discovery and compromise in a more sophisticated PoC.

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.

Further thoughts

While this issue has been raised against the piccolo_admin repository, it technically exists for all file uploads within a piccolo website if an end developer chooses to include the ability to view SVG files inline within their application. Further thought should likely be given to either or both of the following:

Ensuring the documentation for media handling includes some form of warning/recommendation relating to this. Ideally I think it should just provide an example of a code fix and link to security headers to test their own application
Modifying the Piccolo template generation to include the relevant security headers by default. These include things such as xss protection and a content security policy. This site is a great resource for testing the security headers set on a website

Given the need to allow end developers the freedom to allow for SVG upload, removing the ability to upload them entirely is likely out of the picture.

This could also be resolved by making attempts to view attachments in a new tab set the relevant content-disposition header and force the browser to download the file instead of rendering it inline of the website.

What are your thoughts on the approach to take to mitigate this?

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`piccolo-admin`	≥ 1.2.0&&< 1.3.2	1.3.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for piccolo-admin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update piccolo-admin to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pmww-v6c9-7p83 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pmww-v6c9-7p83 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-pmww-v6c9-7p83. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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

O3 Security · Impact-Aware SCA

Is GHSA-pmww-v6c9-7p83 in your dependencies?

O3 detects GHSA-pmww-v6c9-7p83 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works