dbcve.org
Monitoring PlatformApplication · Dahuatech

CVE-2025-8773

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-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
A vulnerability, which was classified as critical, was found in Dinstar Monitoring Platform 甘肃省危险品库监控平台 1.0. Affected is an unknown function of the file /itc/$%7BappPath%7D/login_getPasswordErrorNum.action. The manipulation of the argument userBean.loginName leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

Critical SQL injection vulnerability in Dinstar Monitoring Platform 1.0 allows remote attackers to inject malicious SQL queries via the userBean.loginName parameter in the /itc/${appPath}/login_getPasswordErrorNum.action endpoint. The vulnerability is actively exploited publicly and affects authentication-related functionality, potentially enabling full database compromise and authentication bypass.

MitigationImplement immediate input validation and migrate to parameterized queries/prepared statements for all database operations in affected authentication handlers. Consider restricting network access to the vulnerable interface and deploying a WAF rule as a temporary compensating control until the code fix is implemented.

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
Monitoring PlatformApplication
Affected:= 1.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 monitoring platform
    Locate and inspect the monitoring platform application directory or check the web server for deployed applications. Look for application files, WAR packages, or installation directories that indicate Dinstar or Dahuatech Monitoring Platform is present. Check version information in the application's main configuration files, README, or about page.
    Affected if The installed application is Dinstar Monitoring Platform or Dahuatech Monitoring Platform version 1.0
  2. Verify vulnerable endpoint accessibility
    Attempt to access the /itc/*/login_getPasswordErrorNum.action endpoint on the web server hosting the monitoring platform. This endpoint is part of the authentication module and should respond to HTTP requests.
    Affected if The endpoint responds (returns any HTTP status other than 404), indicating the vulnerable authentication handler is exposed
  3. Inspect login parameter handling
    Examine the application source code or decompiled classes for the login_getPasswordErrorNum action handler. Locate the code that processes the userBean.loginName parameter and trace how it is used in database queries.
    Affected if The code directly incorporates the userBean.loginName parameter into SQL queries without using parameterized queries or input sanitization
  4. Confirm database query construction
    Review the data access layer code that constructs the SQL queries for the password error tracking functionality. Look for string concatenation or string formatting operations that include user-supplied loginName values.
    Affected if SQL queries are built through string concatenation or formatting with the loginName parameter, enabling SQL injection
  5. Check application logs for exploitation indicators
    Review web server access logs and application logs for requests to /itc/*/login_getPasswordErrorNum.action containing SQL injection payloads in the userBean.loginName parameter. Look for unusual SQL syntax or database errors in the logs.
    Affected if Log analysis reveals SQL injection attempts or successful exploitation of this endpoint

A user is affected if they have deployed Dinstar or Dahuatech Monitoring Platform version 1.0 with the login_getPasswordErrorNum.action endpoint accessible and the userBean.loginName parameter processed without parameterized 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

Implement immediate input validation and migrate to parameterized queries/prepared statements for all database operations in affected authentication handlers. Consider restricting network access to the vulnerable interface and deploying a WAF rule as a temporary compensating control until the code fix is implemented.

Fix this in Monitoring Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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