CVE-2026-108571 Xinhu CVE debrief

Who should care

Defenders responsible for Xinhu Rainrock RockOA installations should assess the vulnerability and its potential impact on their systems. This includes administrators, security teams, and IT personnel who manage or monitor these systems.

Why it matters

The SQL injection vulnerability in Xinhu Rainrock RockOA up to 2.7.6 requires attention from defenders to verify system exposure, assess potential impact, and implement necessary mitigations or compensating controls.

• Potential unauthorized database interactions
• Possible data tampering or extraction
• Required verification of inventory and system exposure
• Potential need for compensating controls or mitigations

Technical summary

The vulnerability is located in the kqjcmdModel::returnchuli function of the openkqjAction.php file in the Openkqj Action component of Xinhu Rainrock RockOA up to 2.7.6. The manipulation of the ID argument can lead to SQL injection, allowing remote attackers to interact with the database. This weakness requires attention from defenders to verify system exposure, assess potential impact, and implement necessary mitigations or compensating controls. Affected product deployments should be identified in managed environments, and owners should be assigned for follow-up. The official CVE record and source item provide details about the vulnerability, including its description, CVSS score, and affected versions.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their inventory and assessing the potential impact on their systems.

Recommended defensive actions

• Verify the presence of Xinhu Rainrock RockOA up to 2.7.6 in your inventory
• Assess the potential impact of the SQL injection vulnerability on your systems
• Consider implementing compensating controls to mitigate the vulnerability
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details about the vulnerability, including its description, CVSS score, and affected versions. However, the vendor did not respond to early disclosure, and there is no information on official patches or mitigations.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.