How severe is CVE-2022-1928?

CVE-2022-1928 has a CVSS score of 4.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-1928?

CVE-2022-1928 affects the following packages: code.gitea.io/gitea (Go). Ecosystems affected: Go.

How do I fix CVE-2022-1928?

Update code.gitea.io/gitea to 1.16.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1928 is resolved across your whole dependency graph.

How do I detect CVE-2022-1928 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.gitea.io/gitea, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-1928 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-2022-1928 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-1928, including 1 in-the-wild exploitation 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-2022-1928?

CVE-2022-1928 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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-2022-1928?

CVE-2022-1928 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-2022-1928 published, and has it been updated?

CVE-2022-1928 was published on May 29, 2022 and was last updated on October 28, 2026. 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

MEDIUM severity

CVE-2022-1928 — gitea

MEDIUMFix: go-gitea/gitea@65e0688

CVE-2022-1928 is a medium-severity (CVSS 4.4) Cross-site Scripting (XSS) vulnerability in code.gitea.io/gitea. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for code.gitea.io/gitea — see the affected versions and patch details below.

Cross-site Scripting (XSS) - Stored in go-gitea/gitea

Also known asBIT-gitea-2022-1928GHSA-ph3w-2843-72mxGO-2022-0612

Published

May 29, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

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

1 pkg affected

🐹code.gitea.io/gitea

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) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9 via unfiltered pdfs

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`code.gitea.io/gitea`	all versions	1.16.9`go get code.gitea.io/gitea@v1.16.9`

Affected Products

1 product · 1 configurations

Application

giteagitea

< 1.16.9

range

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) - Stored in GitHub repository go-gitea/gitea …

huntr.devNVDJun 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.gitea.io/gitea, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update code.gitea.io/gitea to 1.16.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1928 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

Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9 via unfiltered pdfs

O3 Security · Impact-Aware SCA

Is CVE-2022-1928 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

May 29, 2022

First exploit

Jun 8, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-1928

GHSA-ph3w-2843-72mx

BIT-gitea-2022-1928

GO-2022-0612

References

Advisorygithub.com · CVE 2022 1928.json Advisorynvd.nist.gov · CVE 2022 1928 Advisorysecurity.gentoo.org · 202210 14 Fixgithub.com · 65e0688a5c9dacad50e71024b7529fdf0e3c2e9c Webhuntr.dev · 6336ec42 5c4d 4f61 ae38 2bb539f433d2 Webgithub.com Webgithub.com · gitea

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting gitea are rated as high or higher (top: critical).

CVE-2026-58428CVE-2026-58314CVE-2026-22874CVE-2026-59765CVE-2026-27761CVE-2026-58511CVE-2026-58419CVE-2026-56657

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026