CVE-2025-2294 in the critical feed json
Kubio AI Page Builder <= 2.5.1 - Unauthenticated Local File Inclusion
published last yr. modified 4mo ago also EUVD-2025-15115
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 78.4%
- EPSS 78.4% chance of exploitation in 30 days, percentile 99.5%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
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.
Is CVE-2025-2294 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-52125)
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
78.36% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-52125 Kubio AI Page Builder 2.5.1 - Local File Inclusion (LFI) webapps, 2025-04-05
- Nuclei template Kubio AI Page Builder <= 2.5.1 - Local File Inclusion nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- extendthemes Kubio AI Page Builder
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
Sources
- CVE List CVE-2025-2294
- NVD CVE-2025-2294
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.