LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25291: Project64 2.3.2 Denial of Service via Plugin Directory

Project64 2.3.2 contains a buffer overflow vulnerability in the Plugin Directory settings field that allows local attackers to crash the application by supplying an excessively long string. Attackers can input a 6000-byte payload into the Plugin Directory field through the Options > Settings > Directories interface to trigger an application crash when settings are reopened.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Project64 2.3.2 is reported vulnerable to a local denial-of-service issue in the Plugin Directory setting. An attacker with local access to the application/settings can supply an overly long value and cause the application to crash when settings are reopened.

Executive priority

Medium priority. This is a local application crash issue with public exploit information, but the supplied sources do not indicate active exploitation or remote compromise risk.

Technical view

The bundle describes a CWE-120 buffer overflow in Project64 2.3.2 affecting the Plugin Directory settings field under the Directories settings interface. The reported impact is application availability loss only, reflected by CVSS 4.0 score 6.9 with high vulnerable-system availability impact and no reported confidentiality or integrity impact.

Likely exposure

Exposure appears limited to systems running Project64 2.3.2 where a local user or local attacker can modify the Plugin Directory setting. The bundle does not support remote network exposure or broader affected versions.

Exploitation context

A public ExploitDB reference exists, so proof-of-concept exploit information is publicly available. KEV is false and the supplied bundle does not state active exploitation in the wild.

Researcher notes

The CVE identifier is CVE-2018-25291, but the bundle lists publication on 2026-04-26 and update on 2026-04-27. Patch evidence is not included in the bundle, so remediation should be tied to vendor guidance rather than an assumed fixed version.

Mitigation direction

  • Identify and prioritize any Project64 2.3.2 installations.
  • Check official Project64/vendor guidance for a fixed or supported version before assuming a patch level.
  • Restrict local access to systems where Project64 is installed, especially shared desktops or lab machines.
  • Avoid allowing untrusted users to modify Project64 settings or configuration files.
  • Monitor crash telemetry or user reports for repeated Project64 crashes related to settings access.

Validation and detection

  • Confirm whether Project64 2.3.2 is installed in the environment.
  • Verify whether users with local access can modify the Plugin Directory setting.
  • Review vendor release notes or advisories for any fixed version or mitigation guidance.
  • In a controlled non-production environment only, validate that the application no longer crashes when handling oversized directory-setting input after remediation.
  • Record the result in vulnerability tracking, including version observed, remediation status, and any vendor guidance reviewed.
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-120: 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-2018-25291 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.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/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
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
6.9CVSS 4.0MediumCVSS:4.0/AV:L/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

6.9Medium
CVSS 4.0 vector shape for CVE-2018-25291Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/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
Pj64-EmuProject642.3.2Listed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.