CVE-2025-61220

7.5

AutoBizLine · com.mysecondline.app

An authentication bypass vulnerability in AutoBizLine com.mysecondline.app version 1.2.91 allows unauthenticated attackers to hijack user sessions and access private personal data.

Executive summary

A critical authentication bypass in AutoBizLine com.mysecondline.app allows unauthenticated remote attackers to compromise user accounts and access sensitive information.

Vulnerability

The application contains an incomplete verification mechanism within its user authentication flow, specifically affecting the /user/get_user/ endpoint. This flaw permits unauthenticated remote attackers to impersonate other users without requiring valid credentials.

Business impact

This vulnerability carries a CVSS score of 7.5, indicating a high severity due to the ease of exploitation and the direct impact on data confidentiality. Successful exploitation allows unauthorized parties to harvest personal user information, which poses significant risks regarding privacy compliance, potential identity theft, and severe reputational damage to the service provider.

Remediation

Immediate Action: Since no specific patch version is currently identified, contact the vendor immediately for security guidance or an emergency update. If an update is unavailable, restrict public access to the affected authentication endpoints at the network perimeter.

Proactive Monitoring: Review web server and application access logs for unusual patterns of authentication requests, particularly those targeting the /user/get_user/ endpoint from anomalous IP addresses.

Compensating Controls: Deploy a Web Application Firewall (WAF) rule to intercept and block unauthorized or malformed requests directed at the user profile retrieval functions.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the security researcher's technical write-up referenced in the CVE record.

Analyst recommendation

Given the high impact on user data confidentiality and the presence of a public proof-of-concept, this vulnerability must be treated with high urgency. Administrators should prioritize identifying instances of the affected version and implementing network-level restrictions or vendor-provided patches as soon as they become available to prevent unauthorized account access.

Sources