LiveActive security incident?Get immediate response
CVE Record

CVE-2021-30153: An issue was discovered in the VisualEditor extension in MediaWiki before 1.31.13, and 1.32.x through 1.35....

An issue was discovered in the VisualEditor extension in MediaWiki before 1.31.13, and 1.32.x through 1.35.x before 1.35.2. . When using VisualEditor to edit a MediaWiki user page belonging to an existing, but hidden, user, VisualEditor will disclose that the user exists. (It shouldn't because they are hidden.) This is related to ApiVisualEditor.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE is a privacy leak in MediaWiki's VisualEditor extension. A logged-in user could infer whether a hidden user account exists when editing that hidden user's user page. The impact is limited to confidentiality, but it matters for organizations that rely on hidden users to protect identities or sensitive moderation history.

Executive priority

Treat this as a moderate privacy issue, not an emergency infrastructure compromise. Patch during the normal security maintenance window, sooner for public wikis or communities where hidden identities protect users, staff, or moderation actions.

Technical view

VisualEditor's ApiVisualEditor path disclosed existence of an existing but hidden MediaWiki user when VisualEditor was used against that user's page. Affected versions are MediaWiki before 1.31.13 and 1.32.x through 1.35.x before 1.35.2. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges, confidentiality only.

Likely exposure

Exposure is likely limited to MediaWiki installations running the VisualEditor extension on affected versions, especially sites using hidden or suppressed users. The CVE data does not identify specific vendors beyond MediaWiki/VisualEditor.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation requires low privileges but no user interaction. The observable harm is disclosure of hidden account existence, not code execution, data modification, or service disruption.

Researcher notes

Evidence supports a narrow CWE-668 exposure-control failure in VisualEditor around hidden user existence checks. Public data does not provide affected CPEs, exploit activity, or broader impact. Keep validation focused on version, extension enablement, and whether hidden users are operationally sensitive.

Mitigation direction

  • Upgrade affected MediaWiki deployments to 1.31.13, 1.35.2, or later fixed releases.
  • Review Wikimedia security guidance for branch-specific update instructions.
  • Inventory MediaWiki sites using the VisualEditor extension.
  • Prioritize sites that use hidden users for privacy, safety, or moderation workflows.

Validation and detection

  • Confirm deployed MediaWiki version is not before 1.31.13 or 1.35.2 on affected branches.
  • Check whether the VisualEditor extension is installed and enabled.
  • Review hidden-user workflows to determine confidentiality impact.
  • Confirm the ApiVisualEditor-related fix is present after updating.
Prepared
Confidence
high
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-668: 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-30153 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:L/UI:N/S:U/C:L/I:N/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:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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-668 · source CWE mapping

Exposure of Resource to Wrong Sphere

Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.