OPNsense 19.1 diag_traceroute.php host cross site scripting

Summaryinfo

A vulnerability labeled as problematic has been found in OPNsense 19.1. The affected element is an unknown function of the file diag_traceroute.php. Executing a manipulation of the argument host can lead to cross site scripting. This vulnerability is tracked as CVE-2019-25372. The attack can be launched remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as problematic was found in OPNsense 19.1. This vulnerability affects an unknown part of the file diag_traceroute.php. The manipulation of the argument host 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. CVE summarizes:

OPNsense 19.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts by exploiting insufficient input validation in the host parameter. Attackers can submit crafted payloads through POST requests to diag_traceroute.php to execute arbitrary JavaScript in the context of a user's browser session.

The weakness was disclosed by Ozer Goker as 46351. The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2019-25372 since 02/15/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1059.007.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:diag_traceroute.php it is possible to find vulnerable targets with Google Hacking.

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 databases at Exploit-DB (46351) and EUVD (EUVD-2019-19423). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• OPNsense

Version

• 19.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion