LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25246: Wikipedia 12.0 Denial of Service via Search

Wikipedia 12.0 contains a denial of service vulnerability that allows unauthenticated attackers to crash the application by submitting oversized input through the search functionality. Attackers can paste a large buffer of repeated characters into the search bar to trigger an application crash.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-25246 is a denial-of-service issue in Wikipedia app version 12.0. An unauthenticated attacker can crash the application through oversized search input. The business impact is availability disruption on systems relying on this app, not data theft or system takeover based on the provided sources.

Executive priority

Prioritize remediation where the app supports business workflows or shared devices. The issue is high-severity for availability, but the provided sources do not indicate data compromise, privilege escalation, or confirmed active exploitation.

Technical view

The record describes Wikipedia 12.0 crashing when oversized repeated input is submitted through search. CVSS 4.0 is 8.7 with network attack vector, low complexity, no privileges, and high vulnerable-system availability impact. No confidentiality or integrity impact is identified. The listed CWE is CWE-306, though that does not clearly match the described input-handling crash.

Likely exposure

Exposure appears limited to environments running Wikipedia version 12.0, likely the Microsoft Store application referenced by the CVE sources. Organizations without this app, or not on version 12.0, are not indicated as affected by the provided evidence.

Exploitation context

A public Exploit-DB reference exists, so proof-of-concept information is publicly available. The source bundle does not show CISA KEV listing or confirmed active exploitation. Treat this as publicly known and easy to trigger, but not confirmed as exploited in the wild.

Researcher notes

Evidence is sparse and centered on the CVE description plus Exploit-DB reference. The affected product naming is generic, and no CPEs are provided. Validate exact package identity, versioning, and vendor status before broad remediation. The CWE mapping appears questionable for the stated crash condition.

Mitigation direction

  • Inventory endpoints for Wikipedia app version 12.0.
  • Check vendor or Microsoft Store guidance for updates or replacement versions.
  • Remove the app where it is not business-required.
  • Prioritize shared, kiosk, classroom, or managed-user systems where crashes cause disruption.

Validation and detection

  • Confirm whether Wikipedia app version 12.0 is installed.
  • Verify the installed version through normal software inventory tooling.
  • Review helpdesk or endpoint telemetry for repeated application crashes.
  • If testing is needed, use a controlled environment and avoid production disruption.
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-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-2018-25246 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.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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
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
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2018-25246Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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
WikipediaWikipedia12.0Listed
Weakness

CWE details

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

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.