CVE-2022-0944
Template injection in connection test endpoint leads to RCE in GitHub repository sqlpad/sqlpad prior to 6.10.1.
- CVSS
- 7.2High
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 8.5%chance of exploitation in the next 30 daystop 5% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 15 Mar 2022analysed here 12 Nov 2026
Summary
Triage
- Attack surface
- Server-side
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- Partly. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| sqlpad sqlpad/sqlpad | < 6.10.1Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- sqlpad:sqlpad
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. Code injection payloads are often obfuscated, so they slip past generic WAF rules.
Also consider: remove eval sinks · RASP
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 10 GitHub proofs of concept
GitHub proofs of concept
- 0xRoqeeb/sqlpad-rce-exploit-CVE-2022-09449 stars
- shhrew/CVE-2022-09447 stars
- FlojBoj/CVE-2022-09445 stars
- Robocopsita/CVE-2022-0944_RCE_POC2 stars
and 6 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 15 Mar 2022Published
- 2 Aug 2024CVE record last updated872 days (about 2 years) later
- 8 Sept 2024First proof-of-concept repository on GitHub (unvetted)36 days later
- 12 Nov 2026Analysed by vulneraibility.com796 days (about 2 years) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | HighThe attacker needs admin-level privileges. | The attacker needs admin-level privileges. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2022-0944 being exploited?
Not confirmed. CVE-2022-0944 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 8.5% probability of exploitation in the next 30 days.
How severe is CVE-2022-0944?
CVE-2022-0944 is rated High with a CVSS score of 7.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-0944?
Yes. A fix has been recorded for CVE-2022-0944. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2022-0944 affect?
CVE-2022-0944 affects sqlpad:sqlpad. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Other links (2)
- huntr.dev /bounties/46630727-d923-4444-a421-537ecd63e7fb
- github.com /sqlpad/sqlpad/commit/3f92be386c6cd3e5eba75d85f0700d3ef54daf73
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.