LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36443: Cross Site Request Forgery vulnerability in imcat 5.4 allows remote attackers to escalate privilege via lac...

Cross Site Request Forgery vulnerability in imcat 5.4 allows remote attackers to escalate privilege via lack of token verification.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-36443 is a high-severity CSRF issue reported in imcat 5.4. A remote attacker may be able to cause a logged-in user to perform unintended privileged actions because token verification is missing. The practical risk depends on whether your organization runs imcat 5.4 and whether privileged users access it in browsers.

Executive priority

Treat this as high priority only where imcat 5.4 is deployed or suspected. The business concern is unauthorized privileged change through a logged-in user, but there is no supplied evidence of active exploitation.

Technical view

The record maps the flaw to CWE-352 and assigns CVSS 3.1 score 8.8, with network attack vector, low complexity, no attacker privileges, and required user interaction. The source description attributes privilege escalation to lack of token verification. Structured affected-product data is incomplete, but the title and description name imcat 5.4.

Likely exposure

Exposure is likely limited to organizations running imcat 5.4. The source bundle does not identify CPEs, downstream packages, hosted services, or broader version ranges, so asset confirmation is required before prioritizing remediation work.

Exploitation context

No CISA KEV listing is provided, and the supplied sources do not state active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF where an authenticated user is induced into a state-changing request.

Researcher notes

Evidence is sparse. The authoritative record names CSRF, missing token verification, imcat 5.4, CVSS 8.8, and CWE-352, but structured affected-product data is n/a. Do not infer additional versions, exploit availability, or patch status without checking project guidance.

Mitigation direction

  • Identify whether imcat 5.4 is present in any environment.
  • Check the imcat project issue and vendor guidance for fixed versions or patches.
  • Restrict administrative access until remediation status is confirmed.
  • Require privileged users to avoid untrusted browsing while authenticated.
  • If maintaining custom code, add CSRF token validation to privileged state-changing actions.

Validation and detection

  • Inventory internet-facing and internal applications for imcat 5.4.
  • Confirm privileged state-changing actions require unpredictable CSRF tokens.
  • Review recent privileged account changes for unauthorized activity.
  • Check whether session cookies use protective attributes such as SameSite.
  • Document remediation status and any compensating controls.
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-36443 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-36443Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

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.