CVE-2014-8681 is a medium-severity (CVSS 6.5) SQL Injection vulnerability in gogs.io/gogs. 5 public exploit references exist, so weaponization risk is real. A fix is available for gogs.io/gogs — see the affected versions and patch details below.
SQL Injection in gogs.io/gogs
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2014-8681 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
gogs.io/gogs🐹github.com/gogits/gogsReal-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
SQL injection vulnerability in the GetIssues function in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.6.x before 0.5.6.1025 Beta allows remote attackers to execute arbitrary SQL commands via the label parameter to user/repos/issues.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | gogs.io/gogs | ≥ 0.3.1&&< 0.5.8 | 0.5.8go get gogs.io/gogs@v0.5.8 |
| 🐹Go | github.com/gogits/gogs | ≥ 0.3.1&&< 0.5.8 | 0.5.8go get github.com/gogits/gogs@v0.5.8 |
Affected Products
gogsgogitsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Gogs - 'label' SQL Injection
by Timo Schmid · Nov 14, 2014
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gogs.io/gogs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gogs.io/gogs to 0.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-8681 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-2014-8681 in your dependencies?
Find it across Go, including transitive dependencies.