SchemaHero 0.23.0 Parameter column.go columnAsInsert column sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 3.65 |
Summary
A vulnerability was found in SchemaHero 0.23.0. It has been classified as critical. This affects the function columnAsInsert in the library plugins/postgres/lib/column.go of the component Parameter Handler. Performing a manipulation of the argument column results in sql injection.
This vulnerability is cataloged as CVE-2026-29953. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in SchemaHero 0.23.0. It has been classified as critical. This affects the function columnAsInsert in the library plugins/postgres/lib/column.go of the component Parameter Handler. The manipulation of the argument column with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL Injection vulnerability in SchemaHero 0.23.0 via the column parameter to the columnAsInsert function in file plugins/postgres/lib/column.go.
It is possible to read the advisory at gist.github.com. This vulnerability is uniquely identified as CVE-2026-29953 since 03/04/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/30/2026). The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-17131). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/04/2026 CVE reserved03/30/2026 Advisory disclosed
03/30/2026 VulDB entry created
03/30/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2026-29953 (🔒)
GCVE (CVE): GCVE-0-2026-29953
GCVE (VulDB): GCVE-100-354219
EUVD: 🔒
Entry
Created: 03/30/2026 19:45Updated: 03/30/2026 20:18
Changes: 03/30/2026 19:45 (55), 03/30/2026 20:18 (1)
Complete: 🔍
Cache ID: 216:BE7:103
No comments yet. Languages: en.
Please log in to comment.