VulnerabilityPublished 29 Jan 2021Updated 30 May 2025

CVE-2020-28404: An Improper Authorization Vulnerability Exists

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:L/S:U/UI:N

Attack Complexity: Low
Attack Vector: Network
Availability: None
Confidentiality: High
Integrity: None
Privileges Required: Low
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2021
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =2019.2.0.6	Fixed in–

AI-suggested

European organizations should immediately assess their use of Star Practice Management Web 2019.2.0.6 and restrict access to the application to trusted internal networks only, implementing network segmentation and firewall rules to limit exposure. Since no patches are currently linked, organizations should implement compensating controls such as enhanced authentication and authorization checks at the web server or application gateway level, including web application firewalls (WAFs) configured to detect and block unauthorized access attempts to billing pages. Regularly audit user permissions and monitor access logs for anomalous activity related to billing page access. If possible, disable or restrict the billing page functionality temporarily until a vendor patch or update is available. Additionally, organizations should engage with the software vendor to obtain updates or patches and apply them promptly once released. Conducting security awareness training for administrators and users about the risks of unauthorized access and maintaining up-to-date incident response plans will further reduce risk.

Description

An 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.

Impact

For European organizations using Star Practice Management Web 2019.2.0.6, this vulnerability poses a significant risk to the confidentiality of billing and financial data. Unauthorized access to billing information can lead to exposure of sensitive client financial details, potentially violating GDPR and other data protection regulations prevalent in Europe. This could result in legal penalties, reputational damage, and loss of client trust. Healthcare and professional service providers relying on this software are particularly at risk, as billing data often contains personally identifiable information (PII) and financial records. The unauthorized disclosure could also facilitate further targeted attacks or fraud attempts. Although the vulnerability does not affect system integrity or availability, the confidentiality breach alone is critical in regulated environments. The absence of known exploits reduces immediate risk, but the ease of exploitation and lack of required user interaction mean attackers could leverage this vulnerability opportunistically if discovered.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:12 UTC

Technical details

References

Community reviews

Related threats