CVE-2024-29667
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 · uneditedSQL Injection vulnerability in Tongtianxing Technology Co., Ltd CMSV6 v.7.31.0.2 through v.7.31.0.3 allows a remote attacker to escalate privileges and obtain sensitive information via the ids 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 Tongtianxing CMSV6 versions 7.31.0.2 through 7.31.0.3. The vulnerability is located in the 'ids' parameter, allowing remote attackers to inject malicious SQL queries. This can lead to privilege escalation and unauthorized access to sensitive database information.
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
- 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.
-
Identify the Tongtianxing CMSV6 installationLocate the CMS installation directory or check the web application banner/version information exposed by the serverAffected if The product is not Tongtianxing CMSV6
-
Determine the installed CMSV6 versionAccess the admin panel, check version info in the system settings, or inspect version files in the CMS root directoryAffected if The version is 7.31.0.2, 7.31.0.3, or falls within the range 7.31.0.2 to 7.31.0.3
-
Identify if the vulnerable ids parameter is exposedReview web application traffic and locate endpoints or features that accept an 'ids' parameter, such as search, filtering, or data retrieval functionsAffected if The application processes user-supplied input through an 'ids' parameter without parameterized queries
-
Verify the ids parameter lacks input sanitizationTest the ids parameter with benign SQL-safe characters and observe the application's response behavior or review the source code handling this parameterAffected if The application does not validate, sanitize, or use parameterized queries for the ids parameter
-
Confirm database access from the ids parameterAttempt to observe database error messages or unexpected behavior when submitting special SQL characters in the ids parameter in a non-production testing environmentAffected if SQL syntax or database errors are returned, indicating direct SQL execution
You are affected if you have Tongtianxing CMSV6 versions 7.31.0.2 through 7.31.0.3 running and the application exposes a functional 'ids' parameter that processes user input without SQL injection protections.
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 dataUpgrade CMSV6 to a version beyond 7.31.0.3 that includes the security patch. If immediate patching is not possible, implement input validation and parameterized queries on the affected 'ids' parameter as a temporary workaround.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29667 — 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-2024-29667 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