Skip to content
Fencer Intel
medium 6.5

CVE-2014-8681 json

SQL Injection in gogs.io/gogs

published 11y ago modified 4mo ago also GHSA-mr6h-chqp-p9g2 , GO-2020-0021 , EUVD-2021-1361

cvss
6.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
4.4%
EPSS 4.4% chance of exploitation in 30 days, percentile 91%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • go gogs.io/gogs 0.5.8
  • go github.com/gogits/gogs 0.5.8

Is CVE-2014-8681 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 Fencer

Timeline

  1. First public exploit (EDB-35237)
  2. Published

Exploit prediction

4.44% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-35237 Gogs - 'label' SQL Injection webapps, 2014-11-14
  • github.com https://github.com/gogits/gogs/commit/83283bca4cb4e0f4ec48a28af680f0d88db3d2c8 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2014/Nov/31 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/129116/Gogs-Label-Search-Blind-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go gogs.io/gogs
>=0.3.1, <0.5.8
0.5.8
go github.com/gogits/gogs
>=0.3.1, <0.5.8
<0.5.8
0.5.8

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

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.