CVE-2025-55210 Vulnerability Analysis & Exploit Details

CVE-2025-55210
Vulnerability Scoring

7.5

/10

Very High Risk

Highly exploitable, CVE-2025-55210 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

Attack Complexity: High
Exploits require significant effort and special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: Low
Some privileges are necessary to exploit the vulnerability.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2025-55210 Details

Status: Analyzed

Last updated: 🕐 27 Feb 2026, 13:05 UTC
Originally published on: 🕔 12 Feb 2026, 17:16 UTC

Time between publication and last update: 14 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2025-55210 Vulnerability Summary

CVE-2025-55210: FreePBX is an open-source web-based graphical user interface (GUI) that manages Asterisk. Prior to 17.0.5 and 16.0.17, FreePBX module api (PBX API) is vulnerable to privilege escalation by authenticated users with REST/GraphQL API access. This vulnerability allows an attacker to forge a valid JWT with full access to the REST and GraphQL APIs on a FreePBX that they've already connected to, possibly as a lower privileged user. The JWT is signed using the api-oauth.key private key. An attacker can generate their own token if they possess this key (e.g., by accessing an affected instance), and specify any scopes they wish (e.g., rest, gql), bypassing traditional authorization checks. However, FreePBX enforces that the jti (JWT ID) claim must exist in the database (api_access_tokens table in the asterisk MySQL database) in order for the token to be accepted. Therefore, the attacker must know a jti value that already exists on the target instance. This vulnerability is fixed in 17.0.5 and 16.0.17.

Assessing the Risk of CVE-2025-55210

Access Complexity Graph

The exploitability of CVE-2025-55210 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-55210

This vulnerability, CVE-2025-55210, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-55210, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-55210, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: High
Exploiting CVE-2025-55210 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: High
CVE-2025-55210 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
Availability: High
CVE-2025-55210 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-55210 References

External References

CWE Common Weakness Enumeration

CWE-270

CAPEC Common Attack Pattern Enumeration and Classification

Using Malicious Files CAPEC-17 An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
Hijacking a Privileged Thread of Execution CAPEC-30 An adversary hijacks a privileged thread of execution by injecting malicious code into a running process. By using a privleged thread to do their bidding, adversaries can evade process-based detection that would stop an attack that creates a new process. This can lead to an adversary gaining access to the process's memory and can also enable elevated privileges. The most common way to perform this attack is by suspending an existing thread and manipulating its memory.
Leverage Executable Code in Non-Executable Files CAPEC-35 An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.

Vulnerable Configurations

cpe:2.3:a:sangoma:freepbx:16.0.2:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.2:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.3:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.3:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.4:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.4:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.5:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.5:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.6:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.6:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.7:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.7:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.8:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.8:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.9:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.9:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.1:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.1:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.2:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.2:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.3:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.3:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.4:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.4:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.5:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.5:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.6:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.6:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.7:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.7:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.8:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.8:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.9:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.9:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.10:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.10:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.11:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.11:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.12:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.12:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.13:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.13:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.14:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.14:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.15:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.15:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.16:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.16:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.17:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.17:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.18:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.18:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.19:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.19:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.20:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.20:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.21:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.21:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.22:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.22:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.23:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.23:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.24:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.24:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.25:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.25:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.26:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.26:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.27:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.27:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.28:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.28:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.29:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.29:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.30:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.30:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.31:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.31:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.32:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.32:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.33:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.33:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.34:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.34:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.35:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.35:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.36:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.36:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.37:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.37:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.38:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.38:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.39:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.39:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.40:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.40:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.41:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.41:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.42:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.42:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.43:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.43:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.44:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.44:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.45:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.45:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.46:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.46:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.47:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.47:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.48:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.48:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.49:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.49:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.50:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.50:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.51:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.10.51:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.11:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.11:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.12:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.12:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.13:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.13:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.14:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.14:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.15:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.15:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.16:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:16.0.16:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.1:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.1:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.2:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.2:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.3:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.3:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.4:*:*:*:*:*:*:*
cpe:2.3:a:sangoma:freepbx:17.0.4:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-55210: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2026-3381 – Compress::Raw::Zlib versions through 2.219 for Perl use potentially insecure versions of zlib. Compress::Raw::Zlib includes a copy of the zlib lib...
CVE-2026-3257 – UnQLite versions through 0.06 for Perl uses a potentially insecure version of the UnQLite library. UnQLite for Perl embeds the UnQLite library. V...
CVE-2026-29126 – Incorrect permission assignment (world-writable file) in /etc/udhcpc/default.script in International Data Casting (IDC) SFX2100 Satellite Receiver ...
CVE-2026-29125 – IDC SFX2100 Satalite Recievers set the `/etc/resolv.conf` file to be world-writable by any local user, allowing DNS resolver tampering that can red...
CVE-2026-29124 – Multiple SUID root-owned binaries are found in /home/monitor/terminal, /home/monitor/kore-terminal, /home/monitor/IDE-DPack/terminal-dpack, and /ho...