LiveActive security incident?Get immediate response
CVE Record

CVE-2025-58952: WordPress Neuronet theme < 1.14.0 - Local File Inclusion vulnerability

Unauthenticated Local File Inclusion in Neuronet < 1.14.0 versions.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-58952 is an unauthenticated local file inclusion flaw in the WordPress Neuronet theme before 1.14.0. If exploitable, it could let an attacker access or influence sensitive local files on the web server. The CVSS score is high at 8.1, but attack complexity is listed as high.

Executive priority

Treat this as a high-priority WordPress exposure item for any site using Neuronet. Prioritize confirming theme presence and version, then patching or applying vendor guidance. Business urgency is highest for public sites handling credentials, customer data, or revenue workflows.

Technical view

The issue is classified as CWE-98 and described as unauthenticated Local File Inclusion in ThemeREX Neuronet versions before 1.14.0. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating network access, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the ThemeREX Neuronet theme, especially versions earlier than 1.14.0. The source bundle does not identify affected CPEs or exact version ranges beyond the title and description.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. The vulnerability is unauthenticated and network reachable, but the CVSS vector lists high attack complexity, so practical exploitation may depend on site-specific conditions.

Researcher notes

Evidence is narrow: the bundle names ThemeREX Neuronet, unauthenticated LFI, CWE-98, CVSS 8.1, and the before-1.14.0 boundary. It does not provide exploit details, vulnerable parameters, PoC status, or vendor advisory text, so validation should avoid assumptions beyond version and theme presence.

Mitigation direction

  • Inventory WordPress sites for the Neuronet theme and record installed versions.
  • Update Neuronet to a non-vulnerable release per ThemeREX or Patchstack guidance.
  • Prioritize any internet-facing WordPress site running Neuronet before 1.14.0.
  • Restrict access to administrative paths where feasible while patch status is confirmed.
  • Review web server logs for suspicious file path or inclusion-related requests.

Validation and detection

  • Confirm whether the Neuronet theme is installed on each WordPress site.
  • Verify the installed theme version is 1.14.0 or later, if vendor guidance confirms that fix level.
  • Check vulnerability management tools for CVE-2025-58952 detection coverage.
  • Review Patchstack and CVE records for updated affected-version or remediation details.
  • Confirm no compensating controls are being mistaken for patch completion.
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 · low confidence lookup

CWE-98: 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-2025-58952 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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
3Timeline 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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2025-58952Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXNeuronetneuronet, n/aunaffected
Weakness

CWE details

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