CVE-2025-30604
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in jiangqie JiangQie Official Website Mini Program jiangqie-official-website-mini-program allows Blind SQL Injection.This issue affects JiangQie Official Website Mini Program: from n/a through <= 1.8.2.
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 confidenceA blind SQL injection vulnerability exists in the JiangQie Official Website Mini Program (versions up to 1.8.2). Attackers can inject malicious SQL queries through user-supplied input, allowing them to infer database information through application behavior changes rather than direct output. The CVSS 7.6 score indicates significant impact requiring immediate attention.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
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.
-
Identify installed version of JiangQie Official Website Mini ProgramLocate the version identifier in the Mini Program's configuration files, manifest.json, or version.php. Common locations include the root directory or a /config/ subdirectory. The version is typically listed as a numeric value like '1.8.2' or similar.Affected if The installed version is 1.8.2 or any lower version number.
-
Review database query code for dynamic SQL constructionSearch the Mini Program source code for SQL query strings that concatenate or embed user-supplied variables directly into query statements. Look for patterns like 'SELECT * FROM' combined with $_GET, $_POST, or request parameters without using prepared statements.Affected if Dynamic SQL queries exist that incorporate user input without parameterized binding.
-
Identify user input acceptance pointsExamine the application's request handlers, API endpoints, and form processing logic. Trace how parameters from GET/POST requests, URL segments, or HTTP headers flow into database operations.Affected if User-provided input is accepted and passed to database query functions.
-
Inspect the database configuration for privilege settingsReview the database connection configuration file to determine what database account permissions are granted to the Mini Program. Check if the account has unnecessary privileges like DROP, DELETE, or administrative access beyond what is required for normal operation.Affected if The database user has excessive privileges beyond read/write operations required for the application.
You are affected if the installed version is 1.8.2 or lower AND user-supplied input is processed through dynamic SQL queries without prepared statements.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements across the application, implement strict input validation, and apply the vendor patch when available. Restrict database account permissions to minimum required operations.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30604 — 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-2025-30604 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