CVE-2023-7333 json
bluelabsio records-mover Table Object sql injection
published 10mo ago modified 4mo ago also GHSA-p3jp-7gj7-h6pr , PYSEC-2026-1864 , EUVD-2026-1470
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
A weakness has been identified in bluelabsio records-mover up to 1.5.4. The affected element is an unknown function of the component Table Object Handler. This manipulation causes sql injection. The attack needs to be launched locally. Upgrading to version 1.6.0 is sufficient to fix this issue. Patch name: 3f8383aa89f45d861ca081e3e9fd2cc9d0b5dfaa. You should upgrade the affected component.
Patch / fix
- pypi records-mover 1.6.0
- bluelabsio records-mover 1.6.0
Is CVE-2023-7333 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:O/RC:C |
| CNA | 3.0 | 5.3 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:O/RC:C |
| CNA | 2.0 | 4.3 | AV:L/AC:L/Au:S/C:P/I:P/A:P/E:ND/RL:OF/RC:C |
| CNA | 4.0 | 4.8 | CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 2.0 | 4.3 | AV:L/AC:L/Au:S/C:P/I:P/A:P |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | records-mover | <1.6.0 |
1.6.0 |
Affected products
- bluelabsio records-mover
Classification
References
-
github.com
/bluelabsio/records-mover/pull/254
issue-tracking, web
-
github.com
/bluelabsio/records-mover/commit/3f8383aa89f45d861ca081e3e9fd2cc9d0b5dfaa
patch, web
-
github.com
/bluelabsio/records-mover/releases/tag/v1.6.0
patch, web
-
vuldb.com
/?id.339566
vdb-entry, technical-description, web
-
vuldb.com
/?ctiid.339566
signature, permissions-required, web
-
github.com
/bluelabsio/records-mover/
product
-
nvd.nist.gov
/vuln/detail/CVE-2023-7333
advisory
-
github.com
/bluelabsio/records-mover
package
-
pypi.org
/project/records-mover
package
-
github.com
/advisories/GHSA-p3jp-7gj7-h6pr
advisory
Sources
- CVE List CVE-2023-7333
- GitHub Advisory GHSA-p3jp-7gj7-h6pr
- NVD CVE-2023-7333
- OSV PYSEC-2026-1864
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.