VulnerabilityPublished 19 Nov 2025

CVE-2025-63224: CVE-2025-63224 is a critical authentication bypass

Source CVE Database V5

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

10.0Critical

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

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

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

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

Bold values are the worst case: easiest to exploit or largest impact.

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).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable 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.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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.
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).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Nov 2025
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

AI-suggested

Given the absence of official patches, European organizations should implement immediate compensating controls. These include strict network segmentation to isolate Itel DAB Encoder devices from general IT and internet-facing networks, minimizing exposure to unauthorized access. Deploy network monitoring and anomaly detection systems focused on JWT token reuse patterns and unusual administrative access attempts. Enforce strong access control policies limiting administrative interface exposure to trusted personnel and IP ranges. Consider disabling remote management features if not essential. Engage with the vendor to obtain firmware updates or security advisories and plan for prompt deployment once available. Additionally, conduct regular security audits and penetration tests targeting these devices to identify potential exploitation attempts. Document and prepare incident response plans specific to this vulnerability to ensure rapid containment if exploitation occurs.

Description

CVE-2025-63224 is a critical authentication bypass vulnerability in the Itel DAB Encoder firmware caused by improper JWT validation. Attackers can reuse a valid JWT token from one device to gain administrative access to any other device running the same firmware, regardless of differing passwords or network configurations. This flaw allows full compromise of affected devices without requiring authentication or user interaction. The vulnerability has a CVSS score of 10, indicating maximum severity with complete impact on confidentiality, integrity, and availability. No patches are currently available, and no known exploits have been reported in the wild. European organizations using these devices in broadcasting or related infrastructure face significant risks of unauthorized control and potential disruption. Mitigation requires strict network segmentation, monitoring for anomalous JWT usage, and vendor engagement for firmware updates. Countries with higher adoption of Itel DAB Encoder devices, especially those with critical digital radio infrastructure, are most at risk.

Impact

For European organizations, especially those involved in digital radio broadcasting, media production, or telecommunications infrastructure using Itel DAB Encoder devices, this vulnerability poses a severe threat. An attacker exploiting this flaw can gain full administrative control over affected devices, allowing them to manipulate broadcast content, disrupt services, or use compromised devices as pivot points for further network intrusion. The ability to bypass authentication without credentials or user interaction increases the risk of widespread compromise, potentially affecting critical communication channels. This could lead to significant operational disruptions, reputational damage, and regulatory consequences under European data protection and cybersecurity laws. The vulnerability's impact extends beyond individual devices to the broader network and service availability, making it a critical concern for national broadcasters and private media companies alike.

Summary

CVE-2025-63224 identifies a critical authentication bypass vulnerability in the Itel DAB Encoder (IDEnc build 25aec8d) firmware. The root cause is improper validation of JSON Web Tokens (JWTs) across devices running the same firmware version. Normally, JWTs are used to authenticate sessions securely, binding tokens to specific devices or users. However, in this case, the firmware fails to verify that a JWT token is device-specific, allowing an attacker who obtains a valid JWT from one device to reuse it on any other device with the same firmware. This bypasses authentication controls entirely, granting administrative privileges without needing valid credentials or network access alignment. The vulnerability affects all devices running the vulnerable firmware, regardless of differing passwords or network environments, enabling full device compromise. The CVSS v3.1 score of 10.0 reflects the vulnerability's ease of exploitation (network attack vector, no privileges or user interaction required) and its severe impact on confidentiality, integrity, and availability. Although no public exploits have been reported yet, the flaw presents a critical risk to any deployment of these devices. The vulnerability is categorized under CWE-287 (Improper Authentication) and CWE-384 (Session Fixation), highlighting the failure in secure session management. No patches or firmware updates have been released at the time of publication, increasing the urgency for mitigation through compensating controls.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-384Session Fixation (opens in a new tab)
Compound weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
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.
Architecture and Design
Invalidate any existing session identifiers prior to authorizing a new user session.
Architecture and Design
For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value.
Operation · Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
OWASP Cheat Sheets
Session Management (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Forging (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Nov 2025, 17:14 UTC

WeaknessesCWE-287, CWE-384

Technical details

References

Community reviews

Related threats