RosarioSIS Improper Access Control vulnerabilityGHSA-prjg-28jg-m3p5
HIGHFix: francoisjacquet/rosariosis@630d3e3GHSA-prjg-28jg-m3p5 is a high-severity (CVSS 7.5) Information Exposure vulnerability in francoisjacquet/rosariosis. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for francoisjacquet/rosariosis — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-prjg-28jg-m3p5.
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
francoisjacquet/rosariosisReal-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
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository francoisjacquet/rosariosis prior to 10.8.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | francoisjacquet/rosariosis | all versions | 10.8.2composer require francoisjacquet/rosariosis:^10.8.2 |
Affected Products
rosariosisrosariosisResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for francoisjacquet/rosariosis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update francoisjacquet/rosariosis to 10.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-prjg-28jg-m3p5 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-prjg-28jg-m3p5 in your dependencies?
Find it across Packagist, including transitive dependencies.