LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47702: OpenBMCS Cross Site Request Forgery (CSRF) via sendFeedback.php

OpenBMCS 2.4 contains a CSRF vulnerability that allows attackers to perform actions with administrative privileges by exploiting the sendFeedback.php endpoint. Attackers can submit malicious requests to trigger unintended actions, such as sending emails or modifying system settings.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

OpenBMCS 2.4 has a cross-site request forgery issue in sendFeedback.php. If an administrator is tricked into interacting with a malicious request while logged in, unintended actions may occur, including sending emails or changing settings. This is not listed as known exploited in CISA KEV, but a public Exploit-DB entry exists.

Executive priority

Treat as a moderate-priority web application risk. Prioritize if OpenBMCS 2.4 supports business-critical operations, is internet-facing, or has many administrators. The main concern is unauthorized integrity changes triggered through administrator interaction.

Technical view

CVE-2021-47702 is CWE-352 in OpenBMCS 2.4. The CVSS 4.0 score is 5.3 with network attack vector, low complexity, no privileges required by the attacker, and user interaction required. Reported impact is low integrity impact through the sendFeedback.php endpoint; confidentiality and availability impacts are not indicated.

Likely exposure

Exposure is limited to organizations running OpenBMCS version 2.4, especially where administrators use the web interface. Risk increases if admin sessions are reachable from general user networks or the internet.

Exploitation context

Sources include a public Exploit-DB reference, so proof-of-concept information appears public. The provided data does not show active exploitation, and the CVE is not marked as CISA KEV.

Researcher notes

The bundle names OpenBMCS 2.4 only. No official patch version is provided in the supplied sources. Public references include Zero Science Lab, VulnCheck, and Exploit-DB. Avoid assuming broader version impact without vendor confirmation.

Mitigation direction

  • Identify any OpenBMCS 2.4 instances in the environment.
  • Check OpenBMCS or vendor guidance for a fixed version or official workaround.
  • Restrict administrative interface access to trusted users and networks where feasible.
  • Train administrators to avoid untrusted links while authenticated to OpenBMCS.
  • Monitor for unexpected feedback emails or unauthorized configuration changes.

Validation and detection

  • Confirm whether OpenBMCS is deployed and record its version.
  • Determine whether version 2.4 is present.
  • Verify whether sendFeedback.php is accessible in deployed instances.
  • Review administrative activity for unexpected emails or settings changes.
  • Check vendor and advisory pages for updated remediation guidance.
Prepared
Confidence
high
Sources
6

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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-47702 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
5.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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
5Source 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
5.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.3Medium
CVSS 4.0 vector shape for CVE-2021-47702Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OPEN BMCSOpenBMCS2.4unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.