dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-2294

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Kubio AI Page Builder plugin for WordPress versions up to 2.5.1 contains a Local File Inclusion vulnerability in the thekubio_hybrid_theme_load_template function, allowing unauthenticated attackers to include and execute arbitrary server files. This enables remote code execution by leveraging path traversal to access and run any PHP file on the system.

MitigationUpdate to version 2.5.2 or later immediately. If patching is not possible, deactivate the plugin as the vulnerability is exploitable without authentication and allows full remote code execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Kubio AI Page Builder plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or check the /wp-content/plugins/ directory for a kubio folder
    Affected if The kubio plugin directory exists in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Kubio AI Page Builder and read the version number shown, or open the main plugin PHP file and look for the Version: header
    Affected if The installed version is 2.5.1 or lower
  3. Verify the vulnerable function is present
    Search the kubio plugin files for the string 'thekubio_hybrid_theme_load_template', typically found in theme-related PHP files within the plugin directory
    Affected if The function thekubio_hybrid_theme_load_template exists in the plugin code
  4. Inspect access logs for path traversal exploitation attempts
    Review web server access logs (Apache/nginx) for requests to the site that include ../ sequences or absolute paths like /etc/passwd, particularly targeting the kubio plugin endpoint
    Affected if Suspicious path traversal requests targeting the vulnerable function appear in logs

A WordPress site is affected if the Kubio AI Page Builder plugin is installed with version 2.5.1 or lower, since the vulnerable thekubio_hybrid_theme_load_template function can be reached without authentication

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.5.2 or later immediately. If patching is not possible, deactivate the plugin as the vulnerability is exploitable without authentication and allows full remote code execution.

Recommended fix Moderate confidence

Latest version on WordPress plugin repository (version higher than 2.5.1)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Kubio AI Page Builder plugin
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, download the latest version from the official WordPress plugin repository at plugins.trac.wordpress.org/plugin/kubio
  6. After updating, verify the new version number in the plugins list to confirm the update was successful

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2294 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2294 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data