CVE-2022-31367 is a high-severity (CVSS 8.8) SQL Injection vulnerability in strapi. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for strapi — see the affected versions and patch details below.
Strapi mishandles hidden attributes within admin API responses
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 CVE-2022-31367.
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
strapinpm@strapi/strapinpmDescription
Strapi before 3.6.10 and 4.x before 4.1.10 mishandles hidden attributes within admin API responses.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | strapi | all versions | 3.6.10npm install strapi@3.6.10 |
| 📦npm | @strapi/strapi | ≥ 4.0.0-next.0&&< 4.1.10 | 4.1.10npm install @strapi/strapi@4.1.10 |
Affected Products
strapistrapiResearch 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 strapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update strapi to 3.6.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31367 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 CVE-2022-31367 in your dependencies?
Find it across npm, including transitive dependencies.