LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25991: ifme - Improper Access Control leads to admin deactivation

In Ifme, versions v5.0.0 to v7.32 are vulnerable against an improper access control, which makes it possible for admins to ban themselves leading to their deactivation from Ifme account and complete loss of admin access to Ifme.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-25991 affects Ifme versions v5.0.0 through v7.32. An administrator can improperly deactivate their own admin account through the ban workflow, causing loss of administrative access. The business risk is operational disruption rather than data theft.

Executive priority

Treat this as a moderate operational availability issue. Prioritize remediation for production Ifme deployments where loss of admin access would delay support, moderation, incident response, or account recovery.

Technical view

The issue is improper access control in Ifme, classified as CWE-284. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H, reflecting network reachability, required privileges and interaction, and high availability impact.

Likely exposure

Exposure is limited to organizations running affected Ifme versions, especially deployments where admins can access moderation or ban functions. No CPEs are provided in the source bundle.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not claim active exploitation. Abuse requires a privileged admin context and user interaction, with the primary outcome being admin deactivation and administrative lockout.

Researcher notes

Primary evidence identifies improper access control causing admin self-ban and loss of admin access. The source bundle does not provide CPEs, exploit proof, active exploitation evidence, or a specific fixed release number.

Mitigation direction

  • Identify all Ifme deployments and confirm running versions.
  • Check vendor guidance and the referenced commit for the access-control fix.
  • Upgrade to a fixed Ifme release when confirmed by the vendor.
  • Maintain more than one administrator or recovery path where operationally possible.

Validation and detection

  • Confirm whether any deployment runs Ifme v5.0.0 through v7.32.
  • Review whether the referenced commit is present in the deployed codebase.
  • In staging, verify admins cannot deactivate their own admin access through ban controls.
  • Confirm administrative recovery procedures exist and are documented.
Prepared
Confidence
medium
Sources
4

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-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-25991 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.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/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
3Source 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.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H2.13.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ifmeorgifmev5.0.0, unspecifiedListed
Weakness

CWE details

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

CWE-284 · source CWE mapping

Improper Access Control

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