CVE-2022-46955
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 · uneditedDynamic Transaction Queuing System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /admin/ajax.php?action=save_queue.
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 confidenceSQL injection vulnerability in Dynamic Transaction Queuing System v1.0 allows remote attackers to inject malicious SQL queries through the unsanitized 'id' parameter at /admin/ajax.php?action=save_queue. This critical flaw enables complete database compromise without authentication.
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= 1.0CVSS 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 Dynamic Transaction Queuing System v1.0 is installedSearch for files named 'ajax.php' in web directories, particularly under /admin/ paths. Check application documentation or source code for version identifier '1.0' or 'Dynamic Transaction Queuing System'.Affected if The application is identified as Dynamic Transaction Queuing System version 1.0
-
Verify ajax.php exists with save_queue actionLocate the ajax.php file in the web root or admin directory. Confirm it contains a handler for 'save_queue' action, typically by searching for 'case "save_queue"' or 'save_queue' function definitions in the code.Affected if The ajax.php file exists and contains a save_queue action handler
-
Inspect id parameter handling in save_queueOpen ajax.php and locate the code handling the save_queue action. Search for usage of $_POST['id'] or $_GET['id'] within that handler. Check if the id value is directly concatenated into an SQL query string without escaping, parameterization, or sanitization functions.Affected if The id parameter is used in a SQL query without prepared statements, escaping functions (like mysqli_real_escape_string), or input validation
-
Confirm web application is accessibleAttempt to access the application's login page or public-facing pages. For unauthenticated exploitation, the /admin/ajax.php endpoint must be reachable over the network.Affected if The web application is online and the /admin/ajax.php endpoint is reachable without authentication
-
Check for existing database compromise indicatorsReview database logs for unusual SQL commands, unexpected tables, or unauthorized user accounts created around the time the vulnerability would be exploitable. Examine web server logs for suspicious requests to /admin/ajax.php?action=save_queue with SQL injection payloads.Affected if Unusual SQL patterns appear in database or web server logs, or unauthorized database changes are detected
A user is affected if they run Dynamic Transaction Queuing System v1.0 with the ajax.php file containing unsanitized id parameter in the save_queue action, and that endpoint is network-accessible.
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 in the ajax.php file, specifically in the save_queue action handler. Apply input validation and least-privilege database user restrictions as defense-in-depth measures.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46955 — 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-46955 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