VulnerabilityPublished 24 Apr 2023Updated 30 May 2025

CVE-2023-26099: Telindus Apsal

Source CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.4Medium

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

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

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

Attack Complexity: Low
Attack Vector: Local
Availability: None
Confidentiality: Low
Integrity: Low
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: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 24 Apr 2023
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 =3.14.2022.235	Fixed in–

AI-suggested

Given the absence of official patches or detailed vendor guidance, European organizations should implement the following mitigations: 1) Restrict local access to systems running Telindus Apsal to trusted personnel only, enforcing strict access control policies and monitoring local user activities. 2) Conduct a thorough review of permission configurations within the application to identify and correct any overly permissive consultation rights. 3) Employ network segmentation and host-based firewalls to limit exposure of affected systems. 4) Implement enhanced logging and alerting for unusual access patterns or permission changes related to consultation functions. 5) Engage with Telindus support or security teams to obtain updates or patches as they become available. 6) Consider deploying compensating controls such as data encryption at rest and in transit to reduce the impact of potential data exposure. 7) Educate users about the risks of privilege misuse and enforce the principle of least privilege for all accounts. These steps go beyond generic advice by focusing on access restriction, configuration auditing, and proactive monitoring tailored to the nature of the vulnerability.

Description

An issue was discovered in Telindus Apsal 3.14.2022.235 b. The consultation permission is insecure.

Impact

For European organizations using Telindus Apsal 3.14.2022.235 b, this vulnerability could lead to unauthorized disclosure or modification of sensitive consultation data. Given that Telindus is a Belgian ICT service provider, the affected software may be deployed primarily in Belgium and potentially in neighboring countries where Telindus operates or supplies solutions. The confidentiality and integrity impacts could compromise client data, internal communications, or operational information, potentially leading to regulatory compliance issues under GDPR if personal data is involved. Although the vulnerability does not affect availability, the unauthorized access could facilitate further attacks or insider threats. Organizations relying on this software for consultation or advisory services should be aware of the risk of privilege escalation or data leakage. The medium severity suggests that while the threat is not critical, it still requires timely mitigation to prevent exploitation, especially in sectors handling sensitive or regulated data such as finance, healthcare, or government.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 14:44 UTC

Technical details

References

Community reviews

Related threats