GHSA-qm2j-qvq3-j29v — silverstripe/framework
MEDIUMGHSA-qm2j-qvq3-j29v is a medium-severity (CVSS 4.3) Information Exposure vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.
Record titles for restricted records can be viewed if exposed by GridFieldAddExistingAutocompleter
Exploitation Status
No confirmed exploitation observed yet
- 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-qm2j-qvq3-j29v.
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-qm2j-qvq3-j29v 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 377,636 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
silverstripe/framework🐘silverstripe/frameworkReal-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
Impact
If a user should not be able to see a record, but that record can be added to a GridField using the GridFieldAddExistingAutocompleter component, the record's title can be accessed by that user.
Base CVSS: 4.3 Reported by: Nick K - LittleMonkey, littlemonkey.co.nz
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/framework | all versions | 4.13.39composer require silverstripe/framework:^4.13.39 |
| 🐘Packagist | silverstripe/framework | ≥ 5.0.0&&< 5.1.11 | 5.1.11composer require silverstripe/framework:^5.1.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/framework to 4.13.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qm2j-qvq3-j29v 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-qm2j-qvq3-j29v can be triaged on real exposure rather than presence alone.
Tailored to GHSA-qm2j-qvq3-j29v. 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-qm2j-qvq3-j29v in your dependencies?
O3 Security finds GHSA-qm2j-qvq3-j29v across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.