CVE-2020-28401
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 improper authorization vulnerability exists in Star Practice Management Web version 2019.2.0.6, allowing an unauthorized user to access WIP details about jobs he should not have access to.
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 confidenceStar Practice Management Web version 2019.2.0.6 contains an improper authorization vulnerability where the application fails to properly validate user permissions before granting access to WIP (Work In Progress) details for jobs. An authenticated user can access sensitive job information belonging to other users or teams they should not have access to, indicating a broken access control or IDOR (Insecure Direct Object Reference) flaw.
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= 2019.2.0.6CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Verify installed versionLocate the version number in the application (typically in Help > About, the login page footer, or the system settings panel). Confirm it displays exactly 2019.2.0.6.Affected if The installed version is 2019.2.0.6.
-
Confirm WIP module is accessibleLog into the application with a standard authenticated user account and navigate to the Work In Progress (WIP) or job details section. Verify the module loads successfully for authenticated users.Affected if The WIP/job details feature is accessible to authenticated users in the application.
-
Test cross-user job accessCreate or use two different authenticated user accounts belonging to different teams. As User A, locate a job/WIP record. Then attempt to access that same job record while logged in as User B (who should not have permission to view User A's jobs). Check if the application returns the job details without proper authorization rejection.Affected if User B can view User A's job/WIP details without receiving an authorization error or access denied message.
-
Inspect job detail request patternsUse browser developer tools or a proxy to capture the HTTP request when accessing a job detail. Examine the URL or API endpoint for direct object references (such as sequential or predictable job IDs). Attempt to modify the job ID parameter to access a different user's job record.Affected if The application uses predictable or directly referenceable URLs/IDs for job records that can be manipulated to access unauthorized data.
You are affected if running version 2019.2.0.6 of Iris Star Practice Management and authenticated users can access job/WIP details belonging to other users or teams they should not have access to.
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 dataImplement proper authorization checks at all endpoints serving WIP/job details to verify the requesting user has legitimate access to the requested resource. Validate user permissions before returning any sensitive data.
- 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-2020-28401 — 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-2020-28401 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