How severe is GHSA-6phg-4wmq-h5h3?

No CVSS score has been assigned to GHSA-6phg-4wmq-h5h3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6phg-4wmq-h5h3?

GHSA-6phg-4wmq-h5h3 affects the following packages: frappe (PyPI), frappe (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-6phg-4wmq-h5h3?

Update frappe to 14.93.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6phg-4wmq-h5h3 is resolved across your whole dependency graph.

How do I detect GHSA-6phg-4wmq-h5h3 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for frappe, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6phg-4wmq-h5h3 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-6phg-4wmq-h5h3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6phg-4wmq-h5h3 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-6phg-4wmq-h5h3?

GHSA-6phg-4wmq-h5h3 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th 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-6phg-4wmq-h5h3?

GHSA-6phg-4wmq-h5h3 is classified as SQL Injection (CWE-89). 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-6phg-4wmq-h5h3 published, and has it been updated?

GHSA-6phg-4wmq-h5h3 was published on March 26, 2025 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Frappe has possibility of SQL injection due to improper validationsGHSA-6phg-4wmq-h5h3

GHSA-6phg-4wmq-h5h3 is a SQL Injection vulnerability in frappe. A fix is available for frappe — see the affected versions and patch details below.

Also known asCVE-2025-30217PYSEC-2026-1391

Published

Mar 26, 2025

Updated

Jul 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6phg-4wmq-h5h3.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐍frappe🐍frappe

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

Frappe is a full-stack web application framework. Prior to versions 14.93.2 and 15.55.0, a SQL Injection vulnerability has been identified in Frappe Framework which could allow a malicious actor to access sensitive information. Versions 14.93.2 and 15.55.0 contain a patch for the issue. No known workarounds are available.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`frappe`	all versions	14.93.2`pip install --upgrade 'frappe==14.93.2'`
🐍PyPI	`frappe`	≥ 15.0.0&&< 15.55.0	15.55.0`pip install --upgrade 'frappe==15.55.0'`

Affected Products

1 product · 2 configurations

Application

frappefrappe

≥ 15.0.0 && < 15.55.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for frappe, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update frappe to 14.93.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6phg-4wmq-h5h3 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

### Impact SQL injection could be achieved via a specially crafted request, which could allow malicious person to gain access to sensitive information. ### Workarounds Upgrading is required, no other workaround is present.

O3 Security · Impact-Aware SCA

Is GHSA-6phg-4wmq-h5h3 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works