Ultimate Bootstrap Elements For ElementorWordPress extension · G5plus
CVE-2024-43140
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in G5Theme Ultimate Bootstrap Elements for Elementor allows PHP Local File Inclusion.This issue affects Ultimate Bootstrap Elements for Elementor: from n/a through 1.4.4.
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 · moderate confidenceA Path Traversal vulnerability in G5Theme Ultimate Bootstrap Elements for Elementor plugin (versions through 1.4.4) allows attackers to perform PHP Local File Inclusion by manipulating file path inputs to access restricted directories and include arbitrary PHP files from the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ultimate Bootstrap Elements For ElementorWordPress extension
< 1.4.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify if the Ultimate Bootstrap Elements for Elementor plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Ultimate Bootstrap Elements For Elementor' or 'G5plus Ultimate Bootstrap Elements For Elementor' in the list of active plugins.Affected if The plugin appears in the installed plugins list regardless of activation status
-
Check the installed plugin versionIn the WordPress plugins list, click on the plugin name or view the plugin files to locate the version number. Alternatively, access the main plugin file (usually ube-init.php or similar) via FTP or file manager and read the version header comment.Affected if The version number displayed is 1.4.4 or lower
-
Identify if the file inclusion functionality is accessibleCheck for AJAX endpoints or frontend shortcodes that accept file path parameters. Common paths to inspect include /wp-admin/admin-ajax.php actions related to the plugin, or look for PHP files in the plugin directory that perform file inclusion operations (include, require, include_once, require_once) with unsanitized user input.Affected if The plugin contains file inclusion code that accepts path parameters from request variables without proper sanitization and this endpoint is accessible to unauthenticated or authenticated users
-
Test for path traversal vulnerabilityIf file inclusion endpoints are identified, examine the code to see if path parameters are validated. Look for patterns like $_GET['file'] or $_POST['path'] being used in inclusion functions without sanitization functions such as basename(), realpath(), or path traversal checks.Affected if The code accepts path parameters and passes them directly to include/require functions without validating that the resolved path stays within an allowed directory
You are affected if the Ultimate Bootstrap Elements for Elementor plugin is installed with version 1.4.4 or lower and contains accessible file inclusion functionality that lacks proper path sanitization.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4.5
Upgrade to a patched version of Ultimate Bootstrap Elements for Elementor that includes proper input validation and path sanitization to prevent directory traversal; if no patch exists, disable the plugin until a fix is available.
Ultimate Bootstrap Elements For Elementor version 1.4.5
- 1. Backup your WordPress site and database before making any changes.
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
- 3. Locate 'Ultimate Bootstrap Elements For Elementor' in the plugin list.
- 4. If an update is available, click 'Update Now' to upgrade to version 1.4.5.
- 5. Alternatively, download version 1.4.5 from the official WordPress plugin repository or the vendor's website.
- 6. Deactivate and delete the current version, then upload and install version 1.4.5.
- 7. After updating, verify the plugin is functioning correctly on your site.
- 8. Test that the path traversal vulnerability is no longer exploitable.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ultimate Bootstrap Elements For Elementor
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43140 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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