CVE-2021-36721
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 · uneditedSysaid API User Enumeration - Attacker sending requests to specific api path without any authorization before 21.3.60 version could get users names from the LDAP server.
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 confidenceAn unauthenticated API endpoint in SysAid before version 21.3.60 allows attackers to enumerate valid usernames by sending requests to a specific API path that returns user information from the LDAP server without requiring any authorization.
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< 21.3.60CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 SysAid installationCheck if SysAid web application is running on your network by accessing the SysAid server URL (typically on port 8080 or 80/443) in a web browser or via curlAffected if SysAid web interface is accessible and responding
-
Determine SysAid versionLog into the SysAid admin console as an administrator and navigate to Admin > SysAid Version, or check the version displayed on the login page footerAffected if Installed version is lower than 21.3.60
-
Check API endpoint exposureSend an unauthenticated HTTP GET request to the API path (commonly /api/v1/users or similar user-related API endpoint) using curl or a browser developer consoleAffected if The API endpoint returns user information or valid usernames without requiring login credentials
-
Verify LDAP integrationIn SysAid admin console, navigate to Admin > LDAP > LDAP Settings to confirm whether LDAP directory integration is configured and enabledAffected if LDAP integration is configured and the vulnerable API endpoint returns LDAP user data without authentication
You are affected if your SysAid installation is version 21.3.60 or lower, the API endpoint is externally or internally accessible without credentials, and LDAP user integration is enabled.
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 · scoped21.3.60
Upgrade SysAid to version 21.3.60 or later to patch the vulnerable API endpoint, or apply any vendor-provided security patch for this issue.
21.3.60 or later
- Upgrade Sysaid Application Programming Interface to version 21.3.60 or later
- After upgrading, verify that the API endpoint no longer returns LDAP user information without authentication
- Confirm the fix by testing the specific API path that was vulnerable (as documented in the original security advisory)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36721 — 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-36721 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