Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 9.3 CRITICALEUVD CVSS 3.1 9.3 CVSS 3.1 · [email protected] · Secondary 9.3 CRITICALCVSS 3.1 · [email protected] · Primary 9.6 CRITICALCVSS_V3 Publisher rating CRITICALFixed by github.com/beego/beego/v2 2.3.6osv · severity unknownFixed by github.com/beego/beego/v2 2.3.6KEV status unknown

cve-program · CVE-2025-30223

Published

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, 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). This vulnerability is fixed in 2.3.6.

Read the publisher's advisory

euvd · EUVD-2025-8839

Published

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, 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). This vulnerability is fixed in 2.3.6.

Read the publisher's advisory

nvd · CVE-2025-30223

Published

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, 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). This vulnerability is fixed in 2.3.6.

Read the publisher's advisory

osv · GHSA-2j42-h78h-q4fg

Published

### 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: ```go return fmt.Sprintf(`%v<input%v%v name="%v" type="%v" value="%v"%v>`, label, id, class, name, fType, value, requiredString) ``` 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 or inject HTML tags directly. The vulnerability can be exploited in two main ways: - Attribute Injection: By injecting code into fields like DisplayName, an attacker can break out of the attribute context and execute JavaScript. - Content Injection: By injecting HTML tags into textarea content, an attacker can execute JavaScript. The `RenderForm()` function returns `template.HTML`, which bypasses Go's automatic HTML escaping, making this vulnerability particularly dangerous. ### PoC Retrieve the following (secret) gist: https://gist.github.com/thevilledev/8fd0cab3f098320aa9daab04be59fd2b To run it: ```go go mod init beego-xss-poc go mod tidy go run poc.go ``` Open your browser and navigate to http://localhost:8080/ The application demonstrates the vulnerability through several examples: - `/profile` - Shows a profile with malicious data in the Display Name and Bio fields - `/admin` - Shows multiple user profiles, including one with malicious data - `/submit` - Allows you to create your own profile with malicious data In addition, you may use this Go test in `templatefunc_test.go`. The test passes, validating the vulnerability. ```go func TestRenderFormXSSVulnerability(t *testing.T) { type UserProfile struct { DisplayName string `form:"displayName,text,Name:"` Bio string `form:",textarea"` } // Test case 1: Attribute injection in input field maliciousUser := UserProfile{ DisplayName: `" onmouseover="alert('XSS')" data-malicious="`, Bio: "Normal bio text", } output := RenderForm(&maliciousUser) // The vulnerable output would contain the unescaped JavaScript if !strings.Contains(string(output), `onmouseover="alert('XSS')"`) { t.Errorf("Expected XSS vulnerability in attribute, but got safe output: %v", output) } // Test case 2: Script injection in textarea maliciousUser2 := UserProfile{ DisplayName: "Normal Name", Bio: `</textarea><script>alert('XSS')</script><textarea>`, } output = RenderForm(&maliciousUser2) // The vulnerable output would contain the unescaped script tag if !strings.Contains(string(output), `</textarea><script>alert('XSS')`) { t.Errorf("Expected XSS vulnerability in textarea content, but got safe output: %v", output) } } ``` ### Impact This is a high-severity vulnerability with the following impacts: - Cross-Site Scripting (XSS): Allows execution of arbitrary JavaScript in the context of the victim's browser. - Session Hijacking: Attackers can steal session cookies and impersonate victims. - Credential Theft: Attackers can create fake login forms to steal credentials. - Account Takeover: Attackers can perform actions on behalf of the victim. - Data Exfiltration: Sensitive data visible in the browser can be stolen. This is particularly concerning in admin panels or user management interfaces where one user's data is displayed to another user (typically an administrator). ### Mitigation The vulnerability can be fixed by properly escaping all user-provided values before inserting them into HTML, for example: ```go // Convert value to string and escape it valueStr := "" if value != nil { valueStr = template.HTMLEscapeString(fmt.Sprintf("%v", value)) } // Escape the name and label escapedName := template.HTMLEscapeString(name) escapedLabel := template.HTMLEscapeString(label) escapedType := template.HTMLEscapeString(fType) return fmt.Sprintf(`%v<input%v%v name="%v" type="%v" value="%v"%v>`, escapedLabel, id, class, escapedName, escapedType, valueStr, requiredString) ```

Read the publisher's advisory

osv · GO-2025-3585

Published

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

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2025-30223

Published

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

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, 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). This vulnerability is fixed in 2.3.6.

Source published
31 Mar 2025 16:17:05 UTC
Source modified
31 Mar 2025 18:21:08 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

euvd · EUVD-2025-8839

Published

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, a Cross-Site Scripting (XSS) vulnerability exists in Beego's RenderForm() function due to improper HTML escaping of user-controlled data. This vulnerabil…

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, 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). This vulnerability is fixed in 2.3.6.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 31, 2025, 4:17:05 PM

dateUpdated: Mar 31, 2025, 6:21:08 PM

1 related source bulletins · separate from aliases

openSUSE-SU-2025:14970-1: govulncheck-vulndb-0.0.20250402T160203-1.1 on GA media

CVE-2025-0312 · CVE-2025-23391 · CVE-2025-29072 · CVE-2025-29868 · CVE-2025-30223 · CVE-2025-31135

Source published
Mar 31, 2025, 4:17:05 PM (timezone not stated)
Source modified
Mar 31, 2025, 6:21:08 PM (timezone not stated)
Saved here
15 Nov 2026 03:40:36 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

nvd · CVE-2025-30223

Published

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, a Cross-Site Scripting (XSS) vulnerability exists in Beego's RenderForm() function due to improper HTML escaping of user-controlled data. This vulnerabil…

Beego is an open-source web framework for the Go programming language. Prior to 2.3.6, 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). This vulnerability is fixed in 2.3.6.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-79

Original publisher date fields

published: 2025-03-31T17:15:42.147

lastModified: 2026-06-17T09:08:23.193

1 source CPE criteria · context only
  • cpe:2.3:a:beego:beego:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
31 Mar 2025 17:15:42 UTC
Source modified
17 Jun 2026 09:08:23 UTC
Saved here
25 Oct 2026 02:24:42 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 9.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

CVSS 3.1 · [email protected] · Primary · 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

osv · GHSA-2j42-h78h-q4fg

Published

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

### 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: ```go return fmt.Sprintf(`%v<input%v%v name="%v" type="%v" value="%v"%v>`, label, id, class, name, fType, value, requiredString) ``` 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 or inject HTML tags directly. The vulnerability can be exploited in two main ways: - Attribute Injection: By injecting code into fields like DisplayName, an attacker can break out of the attribute context and execute JavaScript. - Content Injection: By injecting HTML tags into textarea content, an attacker can execute JavaScript. The `RenderForm()` function returns `template.HTML`, which bypasses Go's automatic HTML escaping, making this vulnerability particularly dangerous. ### PoC Retrieve the following (secret) gist: https://gist.github.com/thevilledev/8fd0cab3f098320aa9daab04be59fd2b To run it: ```go go mod init beego-xss-poc go mod tidy go run poc.go ``` Open your browser and navigate to http://localhost:8080/ The application demonstrates the vulnerability through several examples: - `/profile` - Shows a profile with malicious data in the Display Name and Bio fields - `/admin` - Shows multiple user profiles, including one with malicious data - `/submit` - Allows you to create your own profile with malicious data In addition, you may use this Go test in `templatefunc_test.go`. The test passes, validating the vulnerability. ```go func TestRenderFormXSSVulnerability(t *testing.T) { type UserProfile struct { DisplayName string `form:"displayName,text,Name:"` Bio string `form:",textarea"` } // Test case 1: Attribute injection in input field maliciousUser := UserProfile{ DisplayName: `" onmouseover="alert('XSS')" data-malicious="`, Bio: "Normal bio text", } output := RenderForm(&maliciousUser) // The vulnerable output would contain the unescaped JavaScript if !strings.Contains(string(output), `onmouseover="alert('XSS')"`) { t.Errorf("Expected XSS vulnerability in attribute, but got safe output: %v", output) } // Test case 2: Script injection in textarea maliciousUser2 := UserProfile{ DisplayName: "Normal Name", Bio: `</textarea><script>alert('XSS')</script><textarea>`, } output = RenderForm(&maliciousUser2) // The vulnerable output would contain the unescaped script tag if !strings.Contains(string(output), `</textarea><script>alert('XSS')`) { t.Errorf("Expected XSS vulnerability in textarea content, but got safe output: %v", output) } } ``` ### Impact This is a high-severity vulnerability with the following impacts: - Cross-Site Scripting (XSS): Allows execution of arbitrary JavaScript in the context of the victim's browser. - Session Hijacking: Attackers can steal session cookies and impersonate victims. - Credential Theft: Attackers can create fake login forms to steal credentials. - Account Takeover: Attackers can perform actions on behalf of the victim. - Data Exfiltration: Sensitive data visible in the browser can be stolen. This is particularly concerning in admin panels or user management interfaces where one user's data is displayed to another user (typically an administrator). ### Mitigation The vulnerability can be fixed by properly escaping all user-provided values before inserting them into HTML, for example: ```go // Convert value to string and escape it valueStr := "" if value != nil { valueStr = template.HTMLEscapeString(fmt.Sprintf("%v", value)) } // Escape the name and label escapedName := template.HTMLEscapeString(name) escapedLabel := template.HTMLEscapeString(label) escapedType := template.HTMLEscapeString(fType) return fmt.Sprintf(`%v<input%v%v name="%v" type="%v" value="%v"%v>`, escapedLabel, id, class, escapedName, escapedType, valueStr, requiredString) ```

Source published
31 Mar 2025 16:55:22 UTC
Source modified
10 Sep 2026 03:50:06 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

Publisher rating · CRITICAL

osv · GO-2025-3585

Published

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

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

Source published
1 Apr 2025 21:40:00 UTC
Source modified
4 Feb 2026 02:25:35 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 15:59 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current