LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24635: WordPress EduBlink Core plugin <= 2.0.7 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in DevsBlink EduBlink Core edublink-core allows PHP Local File Inclusion.This issue affects EduBlink Core: from n/a through <= 2.0.7.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24635 affects the WordPress EduBlink Core plugin through version 2.0.7. A logged-in attacker may be able to make the plugin include unintended local files, risking exposure or alteration of sensitive data and service disruption. No public source provided confirms active exploitation.

Executive priority

High priority for organizations using EduBlink-based WordPress sites, especially education or training portals with many user accounts. Inventory immediately and follow vendor guidance. If the plugin is not used, removal is a practical risk reduction step.

Technical view

The CVE describes improper control of a filename used in PHP include/require logic, mapped to CWE-98. The listed impact is PHP Local File Inclusion in DevsBlink EduBlink Core edublink-core <= 2.0.7. CVSS 3.1 is 7.5, with network access, high complexity, low privileges, no user interaction, and high CIA impact.

Likely exposure

Exposure is likely limited to WordPress sites running the EduBlink Core plugin at version 2.0.7 or earlier. The CVSS vector indicates exploitation requires low privileges, so sites allowing user registration or many contributor accounts may face higher practical risk.

Exploitation context

The source bundle does not include exploit code, public exploitation claims, or CISA KEV listing. Attack complexity is rated high, and privileges are required. Treat this as a serious plugin exposure requiring prompt inventory and vendor-guided remediation, not as confirmed mass exploitation.

Researcher notes

Evidence is limited to the CVE record and Patchstack advisory reference. The affected range is stated as through <= 2.0.7, but the bundle does not name a fixed version. Avoid assuming remote unauthenticated exploitation; CVSS indicates PR:L and AC:H.

Mitigation direction

  • Inventory WordPress sites for the EduBlink Core plugin and installed version.
  • Prioritize sites running EduBlink Core 2.0.7 or earlier.
  • Check DevsBlink, WordPress plugin, and Patchstack guidance for a fixed release or workaround.
  • Update only to vendor-confirmed fixed versions when available.
  • Disable or remove the plugin where business impact allows until remediation is confirmed.
  • Restrict WordPress account creation and review low-privilege user access.

Validation and detection

  • Confirm plugin presence and version in WordPress administration or asset inventory.
  • Review web and application logs for unusual plugin-related file access errors.
  • Check whether untrusted users have WordPress accounts on affected sites.
  • Verify remediation against vendor or Patchstack advisory details.
  • Retest version status after updates, removals, or compensating controls.
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-2026-24635 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
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/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
0Timeline 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-24635Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Products and packages named in the record

VendorProductVersion / packageStatus
DevsBlinkEduBlink Coreedublink-core, 0unaffected
Weakness

CWE details

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

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.