vtenext up to 25.02.1 Fax modules/Fax/EditView.php fieldname sql injection

Summaryinfo

A vulnerability was found in vtenext up to 25.02.1. It has been rated as critical. This issue affects some unknown processing of the file modules/Fax/EditView.php of the component Fax. Performing a manipulation of the argument fieldname results in sql injection. This vulnerability was named CVE-2025-71456. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in vtenext up to 25.02.1. This affects an unknown function of the file modules/Fax/EditView.php of the component Fax. The manipulation of the argument fieldname with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

vtenext before 25.02.2 contains an SQL injection vulnerability that allows authenticated low-privileged users to inject SQL by supplying a crafted fieldname parameter to modules/Fax/EditView.php. Attackers can read arbitrary database contents, including password reset tokens stored in vte_userauthtoken, to take over other user accounts.

The advisory is shared at blog.sicuranext.com. This vulnerability is uniquely identified as CVE-2025-71456 since 11/04/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

By approaching the search of inurl:modules/Fax/EditView.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 25.02.2 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• vtenext

Version

• 25.02.0
• 25.02.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion