CVE-2018-25257
SQL Injection in Adianti Framework SystemProfileForm Enables Admin Access
Publication date: 2026-04-12
Last updated on: 2026-04-12
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| adianti | framework | 5.5.0 |
| adianti | framework | 5.6.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2018-25257 is an SQL injection vulnerability in Adianti Framework versions 5.5.0 and 5.6.0. It allows authenticated users to inject malicious SQL code through the "name" field in the SystemProfileForm during profile editing.
This injection flaw enables attackers to manipulate database queries, which can lead to modifying user credentials and escalating privileges, including gaining administrative access.
The vulnerability arises from improper sanitization or neutralization of user input in the profile editing functionality, allowing crafted SQL statements to be executed.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized privilege escalation and account takeover.
- Attackers can inject SQL code to modify user credentials.
- An attacker can escalate their privileges from a normal user to an administrator.
- This leads to full account takeover, compromising authentication and authorization mechanisms.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to inject SQL code into the "name" field of the user profile edit page at the URL: http://localhost/template/index.php?class=SystemProfileForm&method=onEdit.
A practical detection method involves logging in as a normal user and submitting crafted SQL statements in the profile edit form to see if the database queries are manipulated.
For example, you can use curl or similar HTTP clients to send POST requests with SQL injection payloads in the "name" field to test if the system is vulnerable.
- Use curl to send a POST request with an SQL injection payload in the "name" parameter to the profile edit endpoint.
- Example command: curl -X POST -d "name=' OR '1'='1" http://localhost/template/index.php?class=SystemProfileForm&method=onEdit
If the injection is successful, it may allow privilege escalation or modification of user credentials, indicating the presence of the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the profile editing functionality to trusted users only and monitoring for suspicious activity related to profile updates.
Applying input validation and sanitization on the "name" field to prevent SQL injection is critical.
If possible, update or patch the Adianti Framework to a version where this vulnerability is fixed.
As a temporary workaround, consider disabling the profile editing feature or limiting it until a patch is applied.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in Adianti Framework 5.5.0 and 5.6.0 allows attackers to escalate privileges and gain administrative access by manipulating user credentials. This unauthorized access can lead to exposure, modification, or misuse of sensitive personal data stored in the system.
Such a compromise can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require strict controls over access to personal and sensitive data, as well as measures to prevent unauthorized data modification or disclosure.
By enabling attackers to bypass authentication and authorization mechanisms, this vulnerability undermines data protection requirements and could result in violations of these regulations, potentially leading to legal and financial consequences for affected organizations.