Adianti Framework 5.5.0 Profile Edit Endpoint SystemProfileForm Name sql injection

Summaryinfo

A vulnerability classified as critical has been found in Adianti Framework 5.5.0. This affects the function SystemProfileForm of the component Profile Edit Endpoint. This manipulation of the argument Name causes sql injection. This vulnerability appears as CVE-2018-25257. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability classified as critical was found in Adianti Framework 5.5.0. Affected by this vulnerability is the function SystemProfileForm of the component Profile Edit Endpoint. The manipulation of the argument name with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Adianti Framework 5.5.0 and 5.6.0 contains an SQL injection vulnerability that allows authenticated users to manipulate database queries by injecting SQL code through the name field in SystemProfileForm. Attackers can submit crafted SQL statements in the profile edit endpoint to modify user credentials and gain administrative access.

The weakness was presented by Joner De Mello Assolin as 46217. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2018-25257 since 04/12/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

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 (46217). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Adianti Framework

Version

• 5.5.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion