Skip to content

Reflected Cross-site Scripting in Asterisk HTTP Status page

High
chrsmj published GHSA-c8g7-475j-fwcc Oct 14, 2025

Package

core (FreePBX 16)

Affected versions

< 16.0.68.39

Patched versions

16.0.68.39
core (FreePBX 17)
< 17.0.18.38
17.0.18.38

Description

Summary

A Reflected Cross-site scripting vulnerability is present on the Asterisk HTTP Status page.

Description

The Asterisk HTTP status page is exposed by FreePBX and is available by default on v16 via any bound IP address at port 8088. (By default on v17, the HTTP binding is only to localhost IP -- so significantly somewhat less vulnerable.) The vulnerability can be exploited by unauthenticated attackers to obtain cookies from logged-in users, allowing to hijack a session of an administrative user.

Note that HTTPS is also affected -- default is port 8089. ON v17 HTTPS IS BOUND TO :: THE SAME AS v16.

Impact

The theft of admin session cookies allows attackers to gain control over the FreePBX admin interface, enabling them to access sensitive data, modify system configurations, create backdoor accounts, and cause service disruption.

Indicators of Compromise (IoC)

If your v16 or v17 system exposed port 8088 or 8089 on its public IP to hostile networks while you were logged in to the Administrator Control Panel (ACP), then you may be at risk. A thorough review of system access logs is advised, particularly webserver access logs.

Mitigation

Besides updating the core module on supported versions of FreePBX, there are at least three additional ways to mitigate the impact of this issue and others of this class. These ideas should help users of all versions of FreePBX.

Lock down HTTP status page to localhost

  1. Navigate to "Advanced Settings".
  2. Change both the "HTTP Bind Address" and "HTTPS Bind Address" to "127.0.0.1".
  3. Press "Submit" at the bottom of the page.
  4. Click "Apply Config" button in the upper-right corner.
  5. Restart the Asterisk process e.g. reboot the system.

Always logout when you are done

Logging out of the ACP as soon as you are done managing your FreePBX system will invalidate the session and prevent the use of any stolen cookies for subsequent logins.

Prevent hostile access

Do not allow unknown IPs to connect to your system. Consider a VPN, firewall and/or other similar solution(s) to deny access to potential intruders.

Scoring

CVSS 4.0 Base vector string: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
CVSS 4.0 more complete vector string: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:U/AU:Y/R:U/V:D/RE:L/U:Amber
Current CVSS v4.0 Base score is 7.5 (High)
Current CVSS v4.0 more complete score is 4.6 (Medium)
Alternative CVSS v4.1 score is 4.6 (Medium)

See details on scoring on the FreePBX blog at https://www.freepbx.org/watch-what-we-do-with-security-fixes-%f0%9f%91%80/

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v4 base metrics

Exploitability Metrics
Attack Vector Network
Attack Complexity Low
Attack Requirements Present
Privileges Required None
User interaction Active
Vulnerable System Impact Metrics
Confidentiality High
Integrity High
Availability Low
Subsequent System Impact Metrics
Confidentiality None
Integrity None
Availability None

CVSS v4 base metrics

Exploitability Metrics
Attack Vector: This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.
Attack Complexity: This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. These are conditions whose primary purpose is to increase security and/or increase exploit engineering complexity. A vulnerability exploitable without a target-specific variable has a lower complexity than a vulnerability that would require non-trivial customization. This metric is meant to capture security mechanisms utilized by the vulnerable system.
Attack Requirements: This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack. These differ from security-enhancing techniques/technologies (ref Attack Complexity) as the primary purpose of these conditions is not to explicitly mitigate attacks, but rather, emerge naturally as a consequence of the deployment and execution of the vulnerable system.
Privileges Required: This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.
User interaction: This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
Vulnerable System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the VULNERABLE SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the VULNERABLE SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the VULNERABLE SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
Subsequent System Impact Metrics
Confidentiality: This metric measures the impact to the confidentiality of the information managed by the SUBSEQUENT SYSTEM due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
Integrity: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of the SUBSEQUENT SYSTEM is impacted when an attacker makes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging).
Availability: This metric measures the impact to the availability of the SUBSEQUENT SYSTEM resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

CVE ID

CVE-2025-59429

Weaknesses

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Learn more on MITRE.

Credits