LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4273: studygolang search.go Search cross site scripting

A vulnerability classified as problematic was found in studygolang. This vulnerability affects the function Search of the file http/controller/search.go. The manipulation of the argument q leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 97ba556d42fa89dfaa7737e9cd3a8ddaf670bb23. It is recommended to apply a patch to fix this issue. VDB-216478 is the identifier assigned to this vulnerability.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-4273 is a reflected cross-site scripting issue in studygolang's search feature. A crafted search query can cause attacker-controlled script content to be rendered to a user who opens the affected page. Business impact is mainly integrity risk: page content or user interactions could be manipulated in that user's browser.

Executive priority

Treat this as a moderate web application issue. It is not described as data theft or service outage, but public exploit disclosure and remote reachability justify timely patching, especially for public deployments.

Technical view

The issue affects the Search function in http/controller/search.go. The q argument is not handled safely, leading to cross-site scripting. CVSS 3.1 is 4.3 with network attack vector, low complexity, no privileges required, and user interaction required. The cited fix is commit 97ba556d42fa89dfaa7737e9cd3a8ddaf670bb23.

Likely exposure

Exposure is limited to organizations running the studygolang application with the vulnerable search implementation. The source bundle does not identify affected version ranges, package identifiers, or CPEs, so teams must verify by code revision or deployed commit state.

Exploitation context

The vulnerability can be initiated remotely and the exploit was publicly disclosed, according to the source bundle. There is no KEV listing and no cited evidence of active exploitation, so active exploitation should not be claimed from these sources.

Researcher notes

Evidence is clear on vulnerability type, location, CVSS, and patch identifier. Evidence is incomplete on affected versions and deployment prevalence. CWE is listed as CWE-707, though operationally this should be assessed as unsafe neutralization or encoding around reflected search input.

Mitigation direction

  • Apply the referenced upstream patch commit or upgrade to a build containing it.
  • Confirm search query output is safely encoded before rendering in HTML contexts.
  • Review vendor or project guidance for any additional recommended remediation.
  • Prioritize internet-facing studygolang deployments before internal or restricted instances.

Validation and detection

  • Inventory any deployed studygolang instances and identify their source revision.
  • Check whether commit 97ba556d42fa89dfaa7737e9cd3a8ddaf670bb23 is present.
  • Review http/controller/search.go for unsafe handling of the q argument.
  • Run a safe regression test confirming search input is rendered as text, not executable content.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-707: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-4273 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-4273Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
unspecifiedstudygolangn/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-707 · source CWE mapping

Improper Neutralization

Improper Neutralization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.