Forgejo before 15.0.3 contains a stored cross-site scripting vulnerability that allows authenticated attackers to execute arbitrary JavaScript in other users' browsers by setting a full name containing an HTML payload and triggering an Actions run. When the DEFAULT_SHOW_FULL_NAME option is enabled, the run description is assembled server-side with the user's display name interpolated into an HTML string via a translation function that does not escape its arguments, and the frontend renders the result using a Vue v-html binding, causing script execution for any user who views the affected Actions run page.
CVE-2026-59102
Score 5.4 from GitHub Security Advisory (severity: LOW) published 2026-07-02. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EPSS
- 9.8%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 6, 2026
References (4)
- disclosure@vulncheckhttps://codeberg.org/forgejo/forgejo/pulls/13002
- disclosure@vulncheckhttps://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/15.0.3.md
- disclosure@vulncheckhttps://github.com/geo-chen/oss/blob/main/forgejo.md
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/forgejo-stored-xss-via-actions-run-full-name-rendering
Vendor Advisories for CVE-2026-59102(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 23:20 UTCEG score recompute
- 2026-07-06 23:20 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 14:21 UTCMITRE cvelistV5CVSS v4 → 2.1 · severity → MEDIUM
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:02 UTCEG score recompute
- 2026-07-05 23:01 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 22:43 UTCEG score recompute
- 2026-07-04 22:43 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 22:24 UTCEG score recompute
- 2026-07-03 22:24 UTCGHSA enrichment
- 2026-07-02 22:06 UTCEG score recompute
- 2026-07-02 22:06 UTCGHSA enrichment
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-59102?
When was CVE-2026-59102 disclosed?
Is CVE-2026-59102 actively exploited?
What is the CVSS score of CVE-2026-59102?
How do I remediate CVE-2026-59102?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59102
Is Your Infrastructure Affected by CVE-2026-59102?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.