LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33396: Cross Site Request Forgery (CSRF) vulnerability in baijiacms 4.1.4, allows attackers to change the password...

Cross Site Request Forgery (CSRF) vulnerability in baijiacms 4.1.4, allows attackers to change the password or other information of an arbitrary account via index.php.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF flaw reported in baijiacms 4.1.4. If a logged-in user can be tricked into interacting with attacker-controlled content, account details such as passwords could be changed through index.php. The record does not name a fixed version.

Executive priority

Treat as a moderate integrity risk. It can enable account tampering if a user is tricked, but sources do not show active exploitation or a confirmed patch. Prioritize exposed administrative deployments and systems with sensitive accounts.

Technical view

CVE-2021-33396 is CWE-352 with CVSS 3.1 score 6.5: network reachable, low complexity, no attacker privileges, user interaction required, and high integrity impact. The public record describes password or account-information changes via index.php. Structured CPE data is absent.

Likely exposure

Most relevant to internet-accessible baijiacms 4.1.4 deployments, especially where privileged users maintain active browser sessions. Source metadata lacks normalized vendor/product CPEs, so asset discovery must rely on application inventory and version evidence.

Exploitation context

Active exploitation is not stated in the provided sources, and KEV is false. The described attack depends on user interaction and abuses cross-site request behavior to cause account changes, rather than direct unauthenticated server compromise.

Researcher notes

The record is sparse: affected CPE fields are not populated, and the GitHub issue is the only named technical reference. Avoid broad product assumptions beyond baijiacms 4.1.4. Validate exposure through local version evidence and vendor/project guidance.

Mitigation direction

  • Check baijiacms vendor or project guidance for a fixed release or official workaround.
  • Restrict administrative access to trusted networks where operationally possible.
  • Require reauthentication for password and sensitive account changes.
  • Ensure anti-CSRF protections are enabled on state-changing account actions.
  • Prioritize upgrades or retirement for exposed baijiacms 4.1.4 instances.

Validation and detection

  • Inventory public and internal systems for baijiacms 4.1.4.
  • Confirm whether index.php exposes account-management functions.
  • Review application code or configuration for CSRF tokens on sensitive requests.
  • Check logs for unexpected password or account-information changes.
  • Verify whether vendor advisories or project issues identify a patched version.
Prepared
Confidence
medium
Sources
3

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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-33396 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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
2Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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
n/an/an/aListed
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.