CVE-2023-33967 is a high-severity (CVSS 8.2) SQL Injection vulnerability in github.com/megaease/easeprobe. A fix is available for github.com/megaease/easeprobe — see the affected versions and patch details below.
EaseProbe vulnerable to SQL injection when using MySQL/PostgreSQL data checking
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-33967.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/megaease/easeprobeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
An SQL injection issue was discovered in EaseProbe before 2.1.0 when using MySQL/PostgreSQL data checking. This problem has been fixed in v2.1.0; users should upgrade to this version.
The vulnerability was discovered by the Oxeye research team.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/megaease/easeprobe | all versions | 2.1.0go get github.com/megaease/easeprobe@v2.1.0 |
Affected Products
easeprobemegaeaseDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/megaease/easeprobe, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/megaease/easeprobe to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33967 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is CVE-2023-33967 in your dependencies?
Find it across Go, including transitive dependencies.