CVE-2020-28404
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 the Billing page without the appropriate privileges.
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 confidenceThis is an improper authorization (broken access control) vulnerability in Star Practice Management Web version 2019.2.0.6. The application fails to properly enforce authorization checks before displaying the Billing page, allowing unauthorized users to access sensitive billing functionality without the required privileges.
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.
-
Identify installed Star Practice Management Web versionAccess the application admin panel, navigate to About or System Information section, or check the software installer details to find the exact version numberAffected if Version is exactly 2019.2.0.6
-
Locate the Billing page access pointLog into the web application and identify the navigation path to the Billing or billing-related functionality (typically under a Billing, Invoicing, or Finance menu item)Affected if The Billing page functionality exists and is visible in the application navigation
-
Test authorization on Billing page with low-privilege accountCreate or use a user account that does NOT have billing privileges or administrative rights, then attempt to navigate directly to the Billing page URL or click the Billing option in the navigationAffected if The Billing page loads and displays sensitive billing data without returning an authorization error or redirecting to an access-denied page
-
Inspect authorization configuration for Billing endpointIf you have access to application configuration files or admin settings, examine the role-based access control (RBAC) settings for the Billing page to verify if proper privilege checks are definedAffected if No explicit authorization rule exists for the Billing page, or the rule is misconfigured to allow all users
You are affected if running version 2019.2.0.6 AND the Billing page can be accessed by a user account lacking billing privileges.
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 and enforce proper server-side authorization checks to verify user privileges before granting access to the Billing page. Ensure role-based access control (RBAC) is correctly applied to all sensitive endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28404 — 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-28404 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