SQL Injection in Dahua Smart Cloud Gateway Registration Management Platform
CVE-2025-34059 is an SQL injection vulnerability in the Dahua Smart Cloud Gateway Registration Management Platform. Improper sanitization of the username parameter in the login handler allows unauthenticated attackers to inject arbitrary SQL statements, potentially exposing sensitive information. The Shadowserver Foundation observed exploitation evidence on February 5, 2025 UTC. The affected-version range and a fixed version are not established.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation may disclose sensitive information accessible through the application's database. Arbitrary SQL statement injection is supported, but specific data modification, service disruption, or code execution outcomes are not established.
If you can’t patch tonight, do this now.
Until a patch is applied, restrict network access to the Dahua Smart Cloud Gateway Registration Management Platform, especially the /index.php/User/doLogin endpoint, to trusted administrative networks or via VPN only. If feasible, place the application behind an access control layer or WAF capable of detecting and blocking SQL injection payloads. Monitor web server, application, and database logs for suspicious requests targeting the username parameter and for anomalous SQL activity. If the platform is internet-exposed, prioritize temporary isolation or disable external access until remediation is complete.
Patch, then assume compromise.
Apply the vendor-provided fix or update for CVE-2025-34059 as soon as it becomes available. The vulnerable login handler at /index.php/User/doLogin should be corrected to use parameterized queries or prepared statements for the username parameter, with strict server-side input validation and safe query construction. Review database account permissions used by the application and reduce them to the minimum necessary. Because exploitation has been observed, exposed instances should be treated as potentially compromised and investigated for unauthorized database access.
No public exploits tracked yet. Mallory keeps watching.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.