VulnerabilityPublished 12 Oct 2020Updated 30 May 2025

CVE-2020-26546: HelpDeskZ

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High · end of life, no fix coming : replace or isolate affected systems; no fix will be released.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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.
Patch: None coming – the product is end of life

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

Attack Complexity: Low
Attack Vector: Network
Availability: None
Confidentiality: High
Integrity: None
Privileges Required: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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 12 Oct 2020
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

No fix will be released: the affected product is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

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

AI-suggested

Given the absence of official patches due to discontinued support, European organizations should prioritize the following mitigations: 1) Immediate migration to a supported and actively maintained help desk solution to eliminate exposure to this vulnerability. 2) If migration is not immediately feasible, disable the 'RememberMe' auto-login feature in HelpDeskZ to prevent exploitation of the vulnerable code path. 3) Implement web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the RememberMe functionality. 4) Conduct thorough code reviews and consider applying community-developed patches or custom fixes that sanitize inputs related to the RememberMe feature. 5) Restrict network access to the HelpDeskZ application to trusted internal IP ranges to reduce exposure to external attackers. 6) Monitor logs for suspicious activity indicative of SQL injection attempts and unauthorized data access. 7) Ensure regular backups of help desk data are maintained securely to enable recovery in case of compromise.

Description

An issue was discovered in HelpDeskZ 1.0.2. The feature to auto-login a user, via the RememberMe functionality, is prone to SQL injection. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Impact

For European organizations using HelpDeskZ 1.0.2, this vulnerability poses a serious risk to the confidentiality of customer support data, internal communications, and potentially sensitive user information stored within the help desk system. Unauthorized access to such data could lead to privacy violations under GDPR, reputational damage, and potential regulatory penalties. Since the vulnerability requires no authentication and no user interaction, attackers can remotely exploit it to extract data stealthily. Organizations relying on HelpDeskZ for customer support or internal ticketing may face data breaches that compromise both customer and employee information. The lack of vendor support complicates remediation, increasing the window of exposure. Additionally, if attackers gain access to sensitive support tickets, they could leverage this information for further targeted attacks or social engineering campaigns within European enterprises.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats