CVE-2022-30618
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 API users if content types accessible to the authenticated user contain relationships to API users (from:users-permissions). There are many scenarios in which such details from API users can leak in the JSON response within the admin panel, either through a direct or indirect relationship. Access to this information enables a user to compromise these users’ accounts if the password reset API endpoints have been enabled. In a worst-case scenario, a low-privileged user could get access to a high-privileged API account, 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 confidenceAuthenticated admin panel users can view sensitive data (emails, password reset tokens) for API users through content type relationships to users-permissions, enabling account takeover and privilege escalation.
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.0, < 4.1.10CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check your Strapi versionRun `npm list strapi` or check package.json to identify the installed Strapi versionAffected if The version is >= 3.0.0 and < 3.6.10, or >= 4.0.0 and < 4.1.10
-
Identify content types with users-permissions relationshipsReview your Strapi content types in the admin panel or codebase and identify any custom content types that define a relation field linking to the users-permissions user typeAffected if Any custom content type has a relation field pointing to the users-permissions plugin user collection
-
Inspect API responses for sensitive fieldsMake an authenticated API request as an admin user to endpoints serving content types with users-permissions relationships, then inspect the JSON response payload for exposed fields such as `email` or `passwordResetToken`Affected if API responses include email addresses or password reset tokens from user-permissions records
-
Verify admin panel relationship field accessAs an admin user, attempt to access or query content types that reference users-permissions through their API endpoints, checking if relation population exposes user dataAffected if Admin users can populate relationship fields and retrieve sensitive user data through the API
Your environment is affected if you run a vulnerable Strapi version AND have content types with relationships to users-permissions that expose sensitive user fields in API responses to authenticated admin users.
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.104.1.10
Restrict relationship fields to users-permissions content types, disable password reset endpoints if unused, or implement field-level access controls to sanitize sensitive user data from API responses.
Strapi 3.6.10 for v3.x or Strapi 4.1.10 for v4.x
- Identify your current Strapi major version (3.x or 4.x)
- If running Strapi 3.x: Upgrade to version 3.6.10 or later
- If running Strapi 4.x: Upgrade to version 4.1.10 or later
- After upgrading, verify that sensitive user data (emails, password reset tokens) is no longer exposed through content type relationships in the admin panel
- Review user permissions to ensure low-privileged users do not have unnecessary access to content types with relationships to users-permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30618 — 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-30618 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