Skip to main content
VulnerabilityPublished Updated

CVE-2023-26097: Telindus Apsal · Incorrect Authorization

Source CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:U/UI:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =3.14.2022.235
Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should first identify any deployments of Telindus Apsal version 3.14.2022.235 b within their environment. Network segmentation should be enforced to restrict access to the affected application, limiting it to trusted and authenticated internal users only. Implement strict access control policies and monitor for unusual or unauthorized actions within the application. Employ network intrusion detection systems (NIDS) to detect anomalous traffic patterns indicative of exploitation attempts. Since no patches are currently available, consider deploying application-layer firewalls or proxies that can enforce authorization checks or block suspicious requests. Regularly audit logs for signs of unauthorized behavior modification. Additionally, organizations should engage with Telindus or relevant vendors to obtain updates on patch releases and apply them promptly once available. Employee training on recognizing potential exploitation attempts and maintaining strong internal security hygiene will further reduce risk.

Description

An issue was discovered in Telindus Apsal 3.14.2022.235 b. Unauthorized actions that could modify the application behaviour may not be blocked.

References

Community reviews

Loading reviews…