VulnerabilityPublished 29 Jan 2021Updated 30 May 2025

CVE-2020-28403: A Cross-Site Request Forgery (CSRF) vulnerability exists

Source CVE Database V5

Not known to be exploited · CVSS 8.0 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

8.0High

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

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

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

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

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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.

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 or the CVSS exploit maturity 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

2) Implement strict CSRF protections such as synchronizer tokens or double-submit cookies within the application to validate the authenticity of state-changing requests. 3) Enforce least privilege principles by reviewing and restricting user roles and permissions to minimize the impact of potential privilege escalation. 4) Monitor web application logs for unusual privilege changes or administrative account modifications to detect exploitation attempts early. 5) Educate users about phishing and social engineering risks to reduce the likelihood of user interaction with malicious requests. 6) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious CSRF attempts targeting the application endpoints. 7) Conduct regular security assessments and penetration testing focused on CSRF and privilege escalation vectors to identify and remediate weaknesses proactively.

Description

A Cross-Site Request Forgery (CSRF) vulnerability exists in Star Practice Management Web version 2019.2.0.6, allowing an attacker to change the privileges of any user of the application. This can be used to grant himself administrative role or remove the administrative account of the application.

Impact

For European organizations using Star Practice Management Web 2019.2.0.6, this vulnerability poses significant risks. Unauthorized privilege escalation can lead to exposure or manipulation of sensitive patient data, violating GDPR and other data protection regulations. The ability to remove administrative accounts can disrupt operations, causing downtime and loss of control over the system. Healthcare providers and associated entities are particularly at risk due to the sensitive nature of the data handled. The breach of confidentiality and integrity could result in regulatory penalties, reputational damage, and potential harm to patients if medical records are altered or deleted. Additionally, the availability impact could hinder critical healthcare services. Given the high severity and potential for misuse, European healthcare organizations must prioritize addressing this vulnerability to maintain compliance and protect patient safety.

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