CVE-2021-41325
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 · uneditedBroken access control for user creation in Pydio Cells 2.2.9 allows remote anonymous users to create standard users via the profile parameter. (In addition, such users can be granted several admin permissions via the Roles parameter.)
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 · moderate confidenceBroken access control vulnerability in Pydio Cells 2.2.9 allows unauthenticated remote users to create standard user accounts through the user creation endpoint without proper authentication validation. The profile parameter can be manipulated, and the Roles parameter permits assignment of administrative permissions, enabling 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= 2.2.9CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 installed Pydio Cells versionCheck the Pydio Cells version by accessing the admin interface or running the command: `cells --version` or inspecting the application metadataAffected if Installed version is exactly 2.2.9
-
Verify user creation endpoint exposureAttempt to access the user creation API endpoint (typically /a/frontend/ugm/users or similar) without providing authentication credentialsAffected if The endpoint responds without requiring valid authentication (returns 200 OK instead of 401/403)
-
Inspect user creation API parameter handlingSend a test POST request to the user creation endpoint with modified profile or Roles parameters (e.g., set profile to 'admin' or Roles to include administrative role)Affected if The API accepts and processes requests that attempt to set elevated profile values or administrative roles without authentication
-
Check for unauthenticated user account creationUse a tool like curl to send a crafted user creation request without any auth token: `curl -X POST https://<host>/a/frontend/ugm/users -H "Content-Type: application/json" -d '{"login":"testuser","profile":"admin"}'`Affected if A new user account is created successfully without requiring authentication
You are affected if Pydio Cells version 2.2.9 is installed AND the user creation endpoint allows unauthenticated requests that can manipulate profile or Roles parameters to grant elevated permissions.
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.
From vendor dataEnforce proper authentication and authorization checks on all user creation endpoints; restrict the profile and Roles parameters to prevent unauthorized users from creating accounts or assigning elevated permissions. Update to a patched version if available.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41325 — 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-2021-41325 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