Skip to main content
Mallory
HighVulnerability

CVE-2025-34059: SQL Injection in Dahua Smart Cloud Gateway Registration Management Platform

Published Jul 1, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.7High · v4
EPSS0.51%44th percentile
CISA KEVNoNot listed
In the wildReported271 exploitation records in Mallory
IdentifiersCVE-2025-34059CWE-89 · Improper Neutralization of Special…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-34059 exploited in the wild?
Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-34059?
As of Oct 9, 2026, Mallory has found no public exploit for CVE-2025-34059.
Is there a patch for CVE-2025-34059?
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.
How severe is CVE-2025-34059?
CVE-2025-34059 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.51% (44th percentile) as of Oct 9, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.