GHSA-j259-6c58-9m58 — loopback-connector-postgr…
CRITICALFix: loopbackio/loopback-connector-postgresql@d57406cGHSA-j259-6c58-9m58 is a critical-severity (CVSS 9.3) SQL Injection vulnerability in loopback-connector-postgresql. A fix is available for loopback-connector-postgresql — see the affected versions and patch details below.
loopback-connector-postgresql Vulnerable to Improper Sanitization of `contains` Filter
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-j259-6c58-9m58.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-j259-6c58-9m58 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
loopback-connector-postgresqlnpmDescription
Improper input validation on the contains LoopBack filter may allow for arbitrary SQL injection.
Impact
When the extended filter property contains is permitted to be interpreted by the Postgres connector, it is possible to inject arbitrary SQL which may affect the confidentiality and integrity of data stored on the connected database.
This affects users who does any of the following:
- Connect to the database via the DataSource with
allowExtendedProperties: truesetting OR - Uses the connector's CRUD methods directly OR
- Uses the connector's other methods to interpret the LoopBack filter.
Patches
Patch release [email protected] has been published of which resolves this issue.
Workarounds
Users who are unable to upgrade should do the following if applicable:
- Remove
allowExtendedProperties: trueDataSource setting - Add
allowExtendedProperties: falseDataSource setting - When passing directly to the connector functions, manually sanitize the user input for the
containsLoopBack filter beforehand.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | loopback-connector-postgresql | all versions | 5.5.1npm install loopback-connector-postgresql@5.5.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loopback-connector-postgresql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update loopback-connector-postgresql to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j259-6c58-9m58 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j259-6c58-9m58 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j259-6c58-9m58. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j259-6c58-9m58 in your dependencies?
O3 Security finds GHSA-j259-6c58-9m58 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.