dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-32672

HIGH · 8.1 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in g5theme Ultimate Bootstrap Elements for Elementor ultimate-bootstrap-elements-for-elementor allows PHP Local File Inclusion.This issue affects Ultimate Bootstrap Elements for Elementor: from n/a through <= 1.4.9.

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

This is a Local File Inclusion (LFI) vulnerability in the Ultimate Bootstrap Elements for Elementor WordPress plugin. The plugin fails to properly sanitize user-supplied input before using it in PHP include/require statements, allowing attackers to include arbitrary local files. With a CVSS score of 8.1 (HIGH), this can potentially lead to remote code execution if the attacker can control the included file content.

MitigationUpgrade to a patched version of the plugin that implements proper input validation and path sanitization for include/require statements, or remove the plugin if no patch is available.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 plugin installation
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Ultimate Bootstrap Elements for Elementor'. Alternatively, check for the plugin directory at wp-content/plugins/ultimate-bootstrap-elements/ or similar naming convention.
    Affected if The plugin is installed and active in the WordPress environment
  2. Identify installed version
    In WordPress admin, click on the plugin to view its details and note the version number displayed. Alternatively, check the plugin's main PHP file for a 'Version' header in the plugin comment block.
    Affected if The installed version falls within any known affected version range (compare your version to official advisory)
  3. Locate vulnerable include/require code
    Inspect PHP files within the plugin directory, focusing on files that handle page rendering or template inclusion. Search for patterns like 'include($_GET[' or 'require($_REQUEST[' where user-supplied parameters are used directly in file inclusion functions.
    Affected if Such code patterns exist without proper sanitization of the input parameter
  4. Check for accessible vulnerable parameters
    Identify URL parameters used in the plugin (common patterns include '?page=', '?file=', '?template='). Test if these parameters accept path traversal sequences like ../../wp-config.php
    Affected if The plugin accepts and processes path traversal input in include/require functions without validation
  5. Review access controls
    Check whether the vulnerable endpoint requires authentication or is accessible to unauthenticated users. Test the suspected parameter without valid credentials.
    Affected if The vulnerable parameter is accessible to unauthenticated users or low-privilege accounts

A user is affected if the Ultimate Bootstrap Elements for Elementor plugin is installed, the version is within the affected range, and the plugin exposes an unauthenticated endpoint that uses unsanitized user input in PHP include/require statements.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the plugin that implements proper input validation and path sanitization for include/require statements, or remove the plugin if no patch is available.

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-32672 — 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-32672 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