CVE-2022-2921 is a high-severity (CVSS 8.8) CWE-359 vulnerability in notrinos/notrinos-erp. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for notrinos/notrinos-erp — see the affected versions and patch details below.
Exposure of Private Personal Information to an Unauthorized Actor in notrinos/notrinoserp
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
notrinos/notrinos-erpReal-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 Private Personal Information to an Unauthorized Actor in GitHub repository notrinos/notrinoserp prior to v0.7. This results in privilege escalation to a system administrator account. An attacker can gain access to protected functionality such as create/update companies, install/update languages, install/activate extensions, install/activate themes and other permissive actions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | notrinos/notrinos-erp | all versions | 0.7composer require notrinos/notrinos-erp:^0.7 |
Affected Products
notrinoserpnotrinosResearch 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 notrinos/notrinos-erp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update notrinos/notrinos-erp to 0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2921 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2022-2921 in your dependencies?
Find it across Packagist, including transitive dependencies.