PatchSiren cyber security CVE debrief
CVE-2026-88994 All Bootstrap Blocks CVE debrief
The All Bootstrap Blocks WordPress plugin through 1.3.31 does not validate a block attribute before using it to build a filesystem path that is included at render time, allowing users with contributor-level access and above to include arbitrary local files, disclose their contents, and execute PHP where a local file containing PHP code can be reached.
- Vendor
- All Bootstrap Blocks
- Product
- All Bootstrap Blocks
- CVSS
- MEDIUM 6.6
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-18
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-18
- Advisory updated
- 2026-09-18
Who should care
Defenders responsible for WordPress installations with the All Bootstrap Blocks plugin should assess exposure and verify the plugin version, especially for sites with contributor-level access and above. They should also consider the potential impact on their systems and prioritize verification and mitigation efforts accordingly.
Why it matters
Defenders should care about CVE-2026-88994 because it allows arbitrary local file inclusion and PHP execution in the All Bootstrap Blocks WordPress plugin, potentially leading to sensitive information disclosure and code execution. Verification of the plugin version and Lightspeed subsystem status is crucial, especially for WordPress sites with contributor-level access and above.
- Potential arbitrary local file disclosure and contents exposure
- Possible PHP execution where a local file containing PHP code can be reached
- Required verification of plugin version and Lightspeed subsystem status
- Potential impact on WordPress sites with contributor-level access and above
Technical summary
The All Bootstrap Blocks WordPress plugin through 1.3.31 does not validate a block attribute before using it to build a filesystem path that is included at render time, allowing users with contributor-level access and above to include arbitrary local files, disclose their contents, and execute PHP where a local file containing PHP code can be reached. Exploitation requires the plugin's Lightspeed subsystem to be enabled.
Defensive priority
Defenders should prioritize verifying the plugin version and ensuring the Lightspeed subsystem is not enabled if possible.
Recommended defensive actions
- Verify the plugin version and ensure it is up-to-date
- Disable the Lightspeed subsystem if not required
- Monitor for suspicious activity and file access attempts
- Restrict contributor-level access and above to necessary users
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but the scope of affected versions and potential impact require further verification, especially for WordPress sites with contributor-level access and above. Defenders should verify plugin version, Lightspeed subsystem status, and monitor for suspicious activity. The vulnerability allows arbitrary local file inclusion and PHP execution, potentially leading to sensitive information disclosure and code execution.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-88994 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-88994
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-88994 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-88994
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/55b1f0b1-dc15-45d4-beb2-4d1d7a9fe3dd/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.