How severe is CVE-2014-8683?

No CVSS score has been assigned to CVE-2014-8683 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-8683?

CVE-2014-8683 affects the following packages: gogs.io/gogs (Go). Ecosystems affected: Go.

How do I fix CVE-2014-8683?

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-8683 is resolved across your whole dependency graph.

How do I detect CVE-2014-8683 in my Go dependencies?

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.

How do I mitigate CVE-2014-8683 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2014-8683 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2014-8683, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-8683?

CVE-2014-8683 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 79th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-8683?

CVE-2014-8683 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2014-8683 published, and has it been updated?

CVE-2014-8683 was published on June 29, 2021 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2014-8683 — gogs

Fix: gogits/gogs@3abc41c

CVE-2014-8683 is a Cross-site Scripting (XSS) vulnerability in gogs.io/gogs. 2 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.

Cross-site Scripting in Gogs

Also known asGO-2022-0642

Published

Jun 29, 2021

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹gogs.io/gogs

Real-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

Cross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.8 allows remote attackers to inject arbitrary web script or HTML via the text parameter to api/v1/markdown.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`gogs.io/gogs`	≥ 0.3.1&&< 0.5.8	0.5.8`go get gogs.io/gogs@v0.5.8`

Affected Products

1 product · 6 configurations

Application

gogsgogits

≤ 0.5.5

5 versions

0.3.1-90.4.10.4.20.5.00.5.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka…

seclists.orgNVDOct 2018

Cross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka…

packetstormsecurity.comNVDOct 2018

Detection & mitigation playbook

Open-source dependency

Detect
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-8683 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-8683 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works