External risk intelligence

SQL Injection in RockOA Login Function Exposes Sensitive Data

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-63742

The vulnerability resides in an API endpoint used for login functions within a web application. Such components are commonly exposed to the internet to facilitate user access and authentication, making them typical targets for external interaction in standard web application deployments.

SQL Injection

Rockoa

2.7.0

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical SQL injection vulnerability exists in a web application's login function, potentially allowing unauthorized access to sensitive information such as administrator credentials and database details. The issue arises from how specific parameters are handled when users log in.

  • Allows unauthorized access to sensitive data.
  • Matters for protecting customer and business information.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted requests to the login API. The vulnerability exists in the `setwxqyAction` function, which processes `shouji` and `userid` parameters without proper sanitization. This allows an attacker to inject malicious SQL code, potentially leading to the exposure of sensitive data.

  • No authentication required.
  • Inject malicious SQL via parameters.
  • Unauthorized access to sensitive data.

Live Threat

Current exploitation, exposure, and threat context

SQL injection in the login API could expose sensitive system and user data, such as administrator credentials and database structure, when an attacker provides malicious input through the `shouji` and `userid` parameters.

  • Administrator accounts and database structure.
  • Malicious input via `shouji` and `userid` parameters.
  • Unauthorized access to critical information.

Operational Fix

Recommended remediation, mitigation, and detection steps

This SQL injection vulnerability in RockOA affects the login API, potentially exposing sensitive data. Real-world ownership likely falls to the application owners responsible for RockOA, in coordination with infrastructure or platform teams managing its deployment. The first practical step is to identify all instances of RockOA, assess their exposure and criticality, and then confirm the accountable owner to prioritize remediation efforts.

  • Application owners must confirm instances.
  • Verify external reachability and business criticality.
  • Plan remediation based on confirmed risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is RockOA?

RockOA is a web-based office automation software platform, specifically version 2.7.0, used by organizations to manage internal business workflows and administrative tasks. It provides a centralized interface for users to interact with company data, including login and authentication modules that facilitate daily operations.

How does CVE-2025-63742 work?

This vulnerability is a SQL Injection, classified as CWE-89. It occurs when a web application improperly handles user-provided data before using it in a database query. In this case, the `setwxqyAction` function fails to sanitize inputs, allowing an attacker to inject their own database commands to bypass normal security controls.

Do I need to be logged in to trigger this bug?

No, this vulnerability does not require authentication. An attacker can trigger the issue by sending specially crafted requests directly to the affected login API endpoint. However, the flaw is specific to the `shouji` and `userid` parameters; providing standard, non-malicious input to these fields does not initiate the injection.

Is my instance of RockOA at risk?

According to Halo Surface Signal, this vulnerability resides in an API endpoint typically exposed to the internet to support remote login functionality. Because this component is often accessible externally to facilitate user authentication, instances connected to public networks are at a higher risk of being targeted by unauthorized actors.

What should I do to respond to this threat?

The first step is to locate all deployments of RockOA 2.7.0 within your environment to determine which systems are active. Once identified, confirm which instances are reachable from the internet, as these represent the highest priority for risk assessment. Coordinate with the application owners to manage these assets and plan for necessary remediation.

References