DB Elettronica Telecomunicazioni Screen SFT DAB 1.9.3 userManager API session fixiation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in DB Elettronica Telecomunicazioni Screen SFT DAB 1.9.3. Impacted is an unknown function of the component userManager API. The manipulation results in session fixiation. This vulnerability is reported as CVE-2023-53775. The attacker must have access to the local network to execute the attack. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, was found in DB Elettronica Telecomunicazioni Screen SFT DAB 1.9.3. Affected is an unknown code block of the component userManager API. The manipulation with an unknown input leads to a session fixiation vulnerability. CWE is classifying the issue as CWE-384. Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Screen SFT DAB 1.9.3 contains an authentication bypass vulnerability that allows attackers to change user passwords by exploiting weak session management controls. Attackers can reuse IP-bound session identifiers to issue unauthorized requests to the userManager API and modify user credentials without proper authentication.
The weakness was disclosed by Gjoko Krstic as 51456. The advisory is available at exploit-db.com. This vulnerability is traded as CVE-2023-53775 since 12/09/2025. The exploitability is told to be easy. Access to the local network is required for this attack. The exploitation doesn't require any form of authentication. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (51456). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Session fixiationCWE: CWE-384
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/09/2025 CVE reserved12/11/2025 Advisory disclosed
12/11/2025 VulDB entry created
01/02/2026 VulDB entry last update
Sources
Advisory: 51456Researcher: Gjoko Krstic
Status: Not defined
CVE: CVE-2023-53775 (🔒)
GCVE (CVE): GCVE-0-2023-53775
GCVE (VulDB): GCVE-100-335802
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/11/2025 07:24Updated: 01/02/2026 15:47
Changes: 12/11/2025 07:24 (71), 01/02/2026 15:47 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.