Skip to content
Fencer Intel
high 7.3

CVE-2014-8682 in the critical feed json

SQL Injection in Gogs

published 2014-11-21 11 y ago modified 2026-06-17 4 mo ago also GHSA-g6xv-8q23-w2q3 , GO-2022-0831 , EUVD-2021-1320

cvss
7.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
32.6%
EPSS 32.6% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

Multiple SQL injection vulnerabilities in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.6.1105 Beta allow remote attackers to execute arbitrary SQL commands via the q parameter to (1) api/v1/repos/search, which is not properly handled in models/repo.go, or (2) api/v1/users/search, which is not properly handled in models/user.go.

Patch / fix

  • go gogs.io/gogs 0.5.8

Timeline

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

Exploit prediction

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

Exploits and checks

  • EDB-35238 Gogs - 'users'/'repos' '?q' SQL Injection webapps, 2014-11-14
  • Nuclei template Gogs (Go Git Service) - SQL Injection nuclei detection template
  • github.com https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/129117/Gogs-Repository-Search-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2014/Nov/33 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/71187 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 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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

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.