CVE-2022-30617
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn authenticated user with access to the Strapi admin panel can view private and sensitive data, such as email and password reset tokens, for other admin panel users that have a relationship (e.g., created by, updated by) with content accessible to the authenticated user. For example, a low-privileged “author” role account can view these details in the JSON response for an “editor” or “super admin” that has updated one of the author’s blog posts. There are also many other scenarios where such details from other users can leak in the JSON response, either through a direct or indirect relationship. Access to this information enables a user to compromise other users’ accounts by successfully invoking the password reset workflow. In a worst-case scenario, a low-privileged user could get access to a “super admin” account with full control over the Strapi instance, and could read and modify any data as well as block access to both the admin panel and API by revoking privileges for all other users.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStrapi CMS exposes sensitive user data (email addresses and password reset tokens) through relationship fields (created_by, updated_by) in API JSON responses. Any authenticated user with access to content that has relationships to other users can retrieve this information, enabling account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.0, < 3.6.10= 4.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Strapi installation versionCheck the version field in package.json at the project root, or run 'npm list strapi' or 'yarn list strapi' to see the installed Strapi versionAffected if The installed version is >= 3.0.0 and < 3.6.10, or exactly 4.0.0
-
Verify API is enabled and accessibleConfirm the Strapi API layer is active by checking that API routes exist in the ./api folder and the server responds to API requests (e.g., GET requests to content-type endpoints)Affected if The API layer is enabled and responds to requests from authenticated users
-
Confirm authenticated user access to contentLog in as a standard authenticated user (not admin) and attempt to access content entries that have relationships to User type (e.g., created_by, updated_by fields) via API endpointAffected if Authenticated non-admin users can query content and receive JSON responses containing relationship fields
-
Inspect API response for sensitive user fieldsMake an authenticated API request to a content-type with user relationships (e.g., /content-type-name endpoint) and examine the JSON response for 'createdBy' or 'updatedBy' objects containing email addresses or password reset tokensAffected if The API response includes sensitive user data such as email addresses or password reset tokens in relationship fields
You are affected if your Strapi version is 3.0.0 through 3.6.9, exactly 4.0.0, and authenticated users can access the API to retrieve content entries that expose user email addresses or reset tokens in relationship fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.6.10
Update Strapi to the version that patches this vulnerability and audit user access controls to detect any compromised accounts.
Strapi v3: upgrade to >= 3.6.10; Strapi v4: upgrade to latest stable 4.x release
- Backup your Strapi application and database before proceeding with any upgrade
- Review the official Strapi upgrade documentation for your current major version
- For Strapi v3.x users: upgrade to version 3.6.10 or later
- For Strapi v4.x users: upgrade to the latest stable 4.x release (newer than 4.0.0)
- After upgrading, verify that sensitive user fields (email, password reset tokens) are no longer exposed in API responses through relationship fields
- Test the password reset functionality and user relationship queries to confirm the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30617 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-30617 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data