Beego allows Reflected/Stored XSS in Beego's RenderForm() Function Due to Unescaped User Input

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

EPSS

• CVE-2025-30223: 0.61% estimated exploitation activity in the next 30 days; percentile 49.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A Cross-Site Scripting (XSS) vulnerability exists in Beego's RenderForm() function due to improper HTML escaping of user-controlled data. This vulnerability allows attackers to inject malicious JavaScript code that executes in victims' browsers, potentially leading to session hijacking, credential theft, or account takeover. The vulnerability affects any application using Beego's RenderForm() function with user-provided data. Since it is a high-level function generating an entire form markup, many developers would assume it automatically escapes attributes (the way most frameworks do). Details The vulnerability is located in the renderFormField() function in Beego's templatefunc.go file (around lines 316-356). This function directly injects user-provided values into HTML without proper escaping: None of the values (label, id, class, name, value) are properly HTML-escaped before being inserted into the HTML template. This allows attackers to break out of the attribute context…

Published by the source

31 Mar 2025, 16:55 UTC

Last modified by the source

4 Aug 2025, 15:12 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2j42-h78h-q4fg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-30223

Advisory: Beego allows Reflected/Stored XSS in Beego's RenderForm() Function Due to Unescaped User Input
IDs: CVE-2025-30223, GHSA-2j42-h78h-q4fg
Record: https://patchnext.com/advisories/cve-2025-30223 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/beego/beego/v2 2.3.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/beego/beego: affected <= 1.12.14
- Go github.com/beego/beego/v2: affected < 2.3.6; fixed in 2.3.6

## Suggested inspection (read-only)
- Go github.com/beego/beego: check the installed version with your package manager.
- Go github.com/beego/beego/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/beego/beego, github.com/beego/beego/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2j42-h78h-q4fg (GitHub-reviewed advisory GHSA-2j42-h78h-q4fg lists affected ranges: Go github.com/beego/beego/v2 >=0 =0 <=1.12.14)

Commands are suggestions: review each one before running it.