CVE-2022-37146
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 · uneditedThe PlexTrac platform prior to version 1.28.0 allows for username enumeration via HTTP response times on invalid login attempts for users configured to use the PlexTrac authentication provider. Login attempts for valid, unlocked users configured to use PlexTrac as their authentication provider take significantly longer than those for invalid users, allowing for valid users to be enumerated by an unauthenticated remote attacker. Note that the lockout policy implemented in Plextrac version 1.17.0 makes it impossible to distinguish between valid, locked user accounts and user accounts that do not exist, but does not prevent valid, unlocked users from being enumerated.
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 confidenceThe PlexTrac platform prior to version 1.28.0 contains a timing-based username enumeration vulnerability. Authentication attempts for valid, unlocked users configured to use the PlexTrac authentication provider (as opposed to external IdPs) take measurably longer than attempts for invalid usernames, allowing unauthenticated remote attackers to enumerate valid user accounts.
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< 1.28.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
- 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.
-
Determine installed PlexTrac versionAccess the PlexTrac admin dashboard and navigate to the settings or about section to view the platform version number. Alternatively, check the application's startup logs or version file if accessible via CLI.Affected if The installed version is below 1.28.0 (e.g., 1.27.x, 1.26.x, etc.)
-
Confirm PlexTrac authentication provider is in useIn the PlexTrac admin panel, go to Authentication or User Management settings and verify whether the platform is configured to use the built-in PlexTrac authentication provider rather than an external Identity Provider (IdP) such as Okta, Azure AD, or Google.Affected if The platform uses the internal PlexTrac authentication provider for user logins
-
Identify unlocked user accountsIn the admin panel under User Management, review the list of user accounts and check their status. Look for accounts that are both active and not locked out.Affected if There exist active user accounts that are not locked out in the PlexTrac system
-
Verify authentication timing response (optional confirmation)If technically feasible, send two authentication requests: one with a known valid username and one with a random invalid username. Measure the response time difference using a tool like Burp Suite or curl with timing metrics.Affected if Authentication attempts for valid usernames respond measurably slower than invalid usernames, confirming the timing differential exists
The environment is affected if PlexTrac version is below 1.28.0, the internal PlexTrac authentication provider is configured, and there are unlocked user accounts in the system.
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 · scoped1.28.0
Upgrade PlexTrac to version 1.28.0 or later. The lockout policy introduced in version 1.17.0 does not prevent this enumeration for unlocked users, so upgrading is required.
1.28.0
- Upgrade Plextrac to version 1.28.0 or later to resolve the username enumeration vulnerability
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-2022-37146 — 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-37146 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