CVE-2024-13545
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 · uneditedThe Bootstrap Ultimate theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.4.9 via the path parameter. This makes it possible for unauthenticated attackers to include PHP 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 PHP files can be uploaded and included. If php://filter is enabled on the server, this issue may directly lead to Remote Code Execution.
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 confidenceThe Bootstrap Ultimate WordPress theme up to version 1.4.9 contains an unauthenticated Local File Inclusion vulnerability via the 'path' parameter. Attackers can include arbitrary PHP files from the server filesystem, potentially executing malicious PHP code. When php://filter wrappers are enabled on the server, this directly enables Remote Code Execution.
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<= 1.4.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Bootstrap Ultimate theme is installedIn WordPress admin, go to Appearance > Themes to verify the Bootstrap Ultimate theme is active. Note the theme name may appear as 'Bootstrap Ultimate' or 'G5plus Ultimate Bootstrap Elements For Elementor'.Affected if The Bootstrap Ultimate theme (G5plus) is installed and active on the WordPress site.
-
Identify the installed theme versionIn WordPress admin, click on the Bootstrap Ultimate theme to view its details. Locate the version number displayed in the theme information panel.Affected if The displayed version number is 1.4.9 or lower (any version up to and including 1.4.9).
-
Check if the vulnerable endpoint is accessibleIdentify the plugin or theme file that handles the 'path' parameter. This typically appears in AJAX calls or direct URL parameters. Search theme/plugin files for code that uses the 'path' parameter in include, require, or similar functions.Affected if Code exists that processes the 'path' parameter without proper sanitization, allowing unauthenticated access to include files.
-
Review PHP configuration settingsCheck the server's php.ini file for the following settings: allow_url_include and whether php:// wrapper restrictions are in place. Create a PHP info file or check existing configuration.Affected if allow_url_include is set to On, or php://filter wrappers are not explicitly disabled in php.ini.
A site is affected if the Bootstrap Ultimate theme (G5plus) version 1.4.9 or lower is installed and the vulnerable 'path' parameter handling code is present and accessible without authentication.
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 · scopedUpdate the Bootstrap Ultimate theme to the latest version immediately. If updates are unavailable, disable the theme and implement WAF rules to block path traversal patterns in the path parameter. Alternatively, disable php://filter and allow_url_include in php.ini.
Latest version of Ultimate Bootstrap Elements For Elementor (1.5.0 or higher)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Ultimate Bootstrap Elements For Elementor' (or 'Bootstrap Ultimate')
- Check the current version is 1.4.9 or below
- If an update is available, click 'Update Now' to install the latest version
- Verify the update completed successfully
- Confirm the new version number after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13545 — 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-13545 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