dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-34059

HIGH · 8.7 CVSS v4.0 Published 2025-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
An SQL injection vulnerability exists in the Dahua Smart Cloud Gateway Registration Management Platform via the username parameter in the /index.php/User/doLogin endpoint. The application fails to properly sanitize user input, allowing unauthenticated attackers to inject arbitrary SQL statements and potentially disclose sensitive information. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-05 UTC.

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 Dahua Smart Cloud Gateway Registration Management Platform's login endpoint (/index.php/User/doLogin). The username parameter is not properly sanitized, allowing unauthenticated attackers to inject arbitrary SQL statements. This can lead to unauthorized access, sensitive data disclosure, and potential database compromise.

MitigationImplement parameterized queries (prepared statements) for all database interactions in the login function and properly sanitize user input. Apply input validation and consider deploying a web application firewall as a temporary protective measure until the code fix is deployed.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Dahua Smart Cloud Gateway installation
    Identify the application by checking for typical Dahua web service processes, installed packages, or the presence of web files in common installation directories such as /var/www/html/, /opt/, or C:\Program Files\Dahua\
    Affected if The software is present on the system and includes the Registration Management Platform component
  2. Verify vulnerable endpoint exists
    Check for the existence of the file /index.php/User/doLogin within the web root directory of the installation
    Affected if The endpoint file exists in the expected web directory structure
  3. Confirm network accessibility of the login interface
    Verify the web application is reachable by attempting to access the base URL or the /index.php/User/login path via HTTP/HTTPS
    Affected if The application is accessible over the network and accepts requests to the login functionality
  4. Check application version
    Examine version information in the application GUI, configuration files, or HTTP response headers; compare against any available version metadata from the Dahua product documentation or release notes
    Affected if The installed version matches or falls within the affected version range for this CVE (if version ranges become available)
  5. Review access logs for suspicious SQL injection patterns
    Inspect web server access logs for requests to /index.php/User/doLogin containing SQL metacharacters (such as quotes, UNION, SELECT, OR 1=1) in the username parameter

If the Dahua Smart Cloud Gateway Registration Management Platform is installed and the /index.php/User/doLogin endpoint is accessible, the system is affected by this vulnerability regardless of version, as no patch version is specified in the advisory.

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

Implement parameterized queries (prepared statements) for all database interactions in the login function and properly sanitize user input. Apply input validation and consider deploying a web application firewall as a temporary protective measure until the code fix is deployed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34059 — 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-34059 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