CVE-2026-37505: n/a
SQL Injection via ORDER BY clause in V2Board thru 1.7.4. In app/Http/Controllers/Admin/UserController.php, the sort parameter from user input is passed directly to User::orderBy($sort, $sortType) without validation. An authenticated admin can sort users by any database column including password, remember_token, and other sensitive fields, enabling information disclosure through ordering analysis.
AI Analysis
Technical Summary
This vulnerability arises in the V2Board application in the Admin UserController where the 'sort' parameter is used unsafely in a database query's ORDER BY clause. An authenticated admin user can manipulate the 'sort' parameter to order users by any database column, including sensitive ones like password and remember_token. This lack of input validation leads to an SQL Injection vulnerability that can disclose sensitive information by analyzing the ordering results. The CVSS 3.1 score is 4.9, reflecting a medium severity with high confidentiality impact but no integrity or availability impact. No official fix or patch has been documented, and no known exploits are reported in the wild.
Potential Impact
An authenticated administrator can exploit this vulnerability to perform SQL Injection via the ORDER BY clause, potentially disclosing sensitive user data such as passwords and authentication tokens. The impact is limited to information disclosure without affecting data integrity or availability. This could lead to unauthorized access to sensitive information stored in the database.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict administrative access to trusted personnel only and monitor for unusual database query patterns related to user sorting. Avoid using unvalidated user input in database queries. Implement input validation or parameterized queries for the 'sort' parameter to prevent injection.
CVE-2026-37505: n/a
Description
SQL Injection via ORDER BY clause in V2Board thru 1.7.4. In app/Http/Controllers/Admin/UserController.php, the sort parameter from user input is passed directly to User::orderBy($sort, $sortType) without validation. An authenticated admin can sort users by any database column including password, remember_token, and other sensitive fields, enabling information disclosure through ordering analysis.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises in the V2Board application in the Admin UserController where the 'sort' parameter is used unsafely in a database query's ORDER BY clause. An authenticated admin user can manipulate the 'sort' parameter to order users by any database column, including sensitive ones like password and remember_token. This lack of input validation leads to an SQL Injection vulnerability that can disclose sensitive information by analyzing the ordering results. The CVSS 3.1 score is 4.9, reflecting a medium severity with high confidentiality impact but no integrity or availability impact. No official fix or patch has been documented, and no known exploits are reported in the wild.
Potential Impact
An authenticated administrator can exploit this vulnerability to perform SQL Injection via the ORDER BY clause, potentially disclosing sensitive user data such as passwords and authentication tokens. The impact is limited to information disclosure without affecting data integrity or availability. This could lead to unauthorized access to sensitive information stored in the database.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict administrative access to trusted personnel only and monitor for unusual database query patterns related to user sorting. Avoid using unvalidated user input in database queries. Implement input validation or parameterized queries for the 'sort' parameter to prevent injection.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-04-06T00:00:00.000Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69f4cbfccbff5d8610073123
Added to database: 5/1/2026, 3:51:24 PM
Last enriched: 5/1/2026, 4:06:58 PM
Last updated: 5/1/2026, 9:04:39 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.