dbcve.org
RockoaApplication

CVE-2025-63742

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SQL Injection vulnerability in function setwxqyAction in file webmain/task/api/loginAction.php in Xinhu Rainrock RockOA 2.7.0 allowing attackers gain sensitive information, including administrator accounts, password hashes, database structure, and other critical data via the shouji and userid parameters.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A SQL Injection vulnerability exists in the setwxqyAction function within loginAction.php of Xinhu Rainrock RockOA version 2.7.0. The shouji and userid parameters are not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code and extract sensitive data including administrator credentials, password hashes, and complete database structure.

MitigationApply a patch from the vendor that implements parameterized queries or prepared statements for the affected parameters. As an interim measure, deploy a WAF rule to block SQL injection patterns in the shouji and userid parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RockoaApplication
Affected:= 2.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed RockOA version
    Locate and inspect the version file or header in the RockOA installation. Common locations include a version.php file, changelog, or admin panel about page. Compare the version number to 2.7.0.
    Affected if The installed version is exactly 2.7.0 (no patches applied).
  2. Locate the vulnerable loginAction.php file
    Search the web root directory for the file loginAction.php. This file typically resides in the include, app, or similar source directory of the RockOA installation.
    Affected if The file loginAction.php exists and contains a function named setwxqyAction.
  3. Inspect the setwxqyAction function for parameter handling
    Open loginAction.php and locate the setwxqyAction function. Examine how the shouji and userid parameters are handled. Look for direct inclusion in SQL query strings without using parameterized queries, prepared statements, or input sanitization functions.
    Affected if The shouji and/or userid parameters are concatenated directly into SQL queries without proper escaping, parameter binding, or use of parameterized queries.
  4. Verify the affected endpoint is accessible
    Determine if the setwxqyAction function can be triggered via an HTTP request. This typically involves sending a request to the login or user-related endpoint that invokes this action, passing values in the shouji or userid parameters.
    Affected if The application processes requests to the setwxqyAction function and accepts input via the shouji or userid parameters without validation.

You are affected if the installed RockOA version is 2.7.0 and the loginAction.php file contains the setwxqyAction function that uses shouji or userid parameters in unsanitized SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply a patch from the vendor that implements parameterized queries or prepared statements for the affected parameters. As an interim measure, deploy a WAF rule to block SQL injection patterns in the shouji and userid parameters.

Fix this in Rockoa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-63742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-63742 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data