Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2025-2294

Kubio AI Page Builder <= 2.5.1 - Unauthenticated Local File Inclusion

Extend Themes / Kubio AI Page Builder · * to <= 2.5.1

Severity
CVSS 9.8 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
78.4%
First observed
12 Jun 2026
Last observed
18 Oct 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2025-2294 is an unauthenticated Kubio AI Page Builder <= 2.5.1 - Unauthenticated Local File Inclusion. The Kubio AI Page Builder plugin for WordPress is vulnerable to Local File Inclusion in all versions up to,...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence. Also confirmed by third-party sources.

Who is affected?

Extend Themes / Kubio AI Page Builder * to <= 2.5.1.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

Kubio AI Page Builder <= 2.5.1 - Unauthenticated Local File Inclusion

The Kubio AI Page Builder plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.5.1 via thekubio_hybrid_theme_load_template function. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files.

This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

extendthemes Affected
Kubio AI Page Builder
Through 2.5.1
Published
28 Mar 2025
Exploited Since
12 Jun 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nuclei_scanner wordpress php

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

The Shadowserver

Recorded 06 Jul 2026

A trusted third party reported exploitation.

Active exploitation observed

Previdian sensor

First observed 12 Jun 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
The Shadowserver First 2025-06-24 00:00 UTC
Previdian Sensors 2026-09-18 12:55 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

17

Attempts observed

11

Unique attacker IPs

9

Attacker countries

BG · CH · DE · HK · JP · LT · NL · US · YE

10

Sensors observed

CVE-2025-2294 exploitation attempts over the last 88 days

Daily events observed by Previdian sensors

Updated 24 Oct 2026

0
2
0
0
0
0
0
0
0
0
0
0
0
0
1
0
2
0
0
0
0
0
1
0
1
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
1
0
0
1
0
0
0
1
0
0
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
29 Jul 16 Aug 3 Sep 21 Sep 24 Oct

First observed 12 Jun 2026 · Last observed 18 Oct 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
1
4
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.8 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

78.4%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. 14:20 UTC

    Public PoC available

    Public proof-of-concept code published

  2. 00:34 UTC

    Indicators of compromise added (19)

    Indicators of compromise recorded

  3. 00:34 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  4. 00:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  5. 00:00 UTC

    Nuclei template available

    Scanner coverage available

  6. 04:22 UTC

    CVE published

    Vulnerability disclosed publicly

  7. 18:41 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2025-2294

Sample API response
{
  "cve_id": "CVE-2025-2294",
  "confidence": "Confirmed",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.7836,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 17, "sensors": 10 }
}