IPFire up to 2.21 Request updatexlrator.cgi MAX_DISK_USAGE/MAX_DOWNLOAD_RATE cross site scripting

Summaryinfo

A vulnerability, which was classified as problematic, has been found in IPFire up to 2.21. This affects an unknown part of the file updatexlrator.cgi of the component Request Handler. This manipulation of the argument MAX_DISK_USAGE/MAX_DOWNLOAD_RATE causes cross site scripting. This vulnerability is handled as CVE-2019-25396. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability has been found in IPFire up to 2.21 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file updatexlrator.cgi of the component Request Handler. The manipulation of the argument MAX_DISK_USAGE/MAX_DOWNLOAD_RATE with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. 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. As an impact it is known to affect integrity. The summary by CVE is:

IPFire 2.21 Core Update 127 contains a reflected cross-site scripting vulnerability in the updatexlrator.cgi script that allows attackers to inject malicious scripts through POST parameters. Attackers can submit crafted requests with script payloads in the MAX_DISK_USAGE or MAX_DOWNLOAD_RATE parameters to execute arbitrary JavaScript in users' browsers.

The weakness was released by Ozer Goker as 46344. It is possible to read the advisory at exploit-db.com. This vulnerability is known as CVE-2019-25396 since 02/18/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

It is possible to download the exploit 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 (46344). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• IPFire

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion