CVE-2022-25404
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 · uneditedTongda2000 v11.10 was discovered to contain a SQL injection vulnerability in delete.php via the DELETE_STR parameter.
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 confidenceA SQL injection vulnerability exists in Tongda2000 v11.10 within the delete.php file. The DELETE_STR parameter is not properly sanitized, allowing attackers to inject malicious SQL queries. This could enable unauthorized database access, data exfiltration, or manipulation.
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= 11.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Tongda2000 installationLocate the Tongda2000 web application directory on your server. This is typically found in the web server root (e.g., /var/www/html/ or C:\inetpub\wwwroot\) or within a dedicated application folder.Affected if Tongda2000 is not present on the system, then this CVE does not apply.
-
Check installed versionLocate and read the version file or configuration file within the Tongda2000 installation directory that contains the version number. Compare your installed version to the affected version 11.10.Affected if The installed version is 11.10, the system falls within the affected range.
-
Locate delete.php fileSearch for the delete.php file within the Tongda2000 installation directory. This file handles deletion operations in the application.Affected if The delete.php file exists and is part of the active Tongda2000 v11.10 installation.
-
Inspect DELETE_STR parameter handlingExamine the delete.php source code and search for usage of the DELETE_STR parameter. Determine whether this parameter is directly used in SQL queries without proper sanitization or parameterized queries.Affected if The DELETE_STR parameter is used in SQL queries without prepared statements or parameterized queries, indicating the vulnerability is present.
-
Verify input validation for DELETE_STRReview the delete.php file to check if there is any input validation, sanitization, or escaping functions applied to the DELETE_STR parameter before it is used in database operations.Affected if No input validation or sanitization exists for DELETE_STR, the application is vulnerable to SQL injection.
A system is affected if it runs Tongda2000 version 11.10 and the delete.php file processes the DELETE_STR parameter without parameterized queries or input validation.
Generated from the published advisory. Verify against your own configuration.
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 dataRemediate by implementing parameterized queries or prepared statements for the DELETE_STR parameter in delete.php, and add proper input validation. Apply the vendor patch if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25404 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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