GHSA-9gv2-2m38-j6cx is a critical-severity (CVSS 9.8) SQL Injection vulnerability in bedita/bedita. A fix is available for bedita/bedita — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
bedita/beditaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
BEdita through 4.0.0-RC2 allows SQL injection during a save operation for a relation with parameters due to a lack of JSON escaping.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | bedita/bedita | all versions | 4.0.0composer require bedita/bedita:^4.0.0 |
Affected Products
beditabeditaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bedita/bedita, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bedita/bedita to 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9gv2-2m38-j6cx 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
Is GHSA-9gv2-2m38-j6cx in your dependencies?
Find it across Packagist, including transitive dependencies.