Plugins · builderall-cheetah-for-wp · data as of 2026-11-04
Is Builderall for WordPress safe? Known vulnerabilities and latest version
- Status
- Closed 2026-08-19
- Known issues on record
- 7
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate builderall-cheetah-for-wp && wp plugin delete builderall-cheetah-for-wp
Check your version
Known vulnerabilities
7 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 7 record(s) do not state which versions are affected.
medium 6.4 CVE-2026-15820 · published 2026-09-10
Stored cross-site scripting (XSS) in Builderall for WordPress (3.0.2 and older)
- Affected
- 3.0.2 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Builderall for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Photo Module 'attributes' Setting in all versions up to, and including, 3.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
medium 4.3 CVE-2026-15823 · published 2026-09-10
Missing authorization check in Builderall for WordPress (3.0.2 and older)
- Affected
- 3.0.2 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Builderall Cheetah For Wp plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the disable() function in versions up to, and including, 3.0.2. The wp_ajax_ba_cheetah_disable AJAX handler is registered without any capability or nonce verification, and the target post_id is sourced directly from user-controlled $_POST['ba_cheetah_data']['post_id']. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disable the page builder layout on arbitrary posts by setting the _ba_cheetah_enabled post meta to false, including on posts owned by other users.
medium 6.4 CVE-2026-15796 · published 2026-09-10
Stored cross-site scripting (XSS) in Builderall for WordPress (3.0.2 and older)
- Affected
- 3.0.2 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Builderall for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'bg_video_service_url' Setting in all versions up to, and including, 3.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
low 3.7 CVE-2026-11882 · published 2026-08-01
Missing authorization check in Builderall for WordPress (older than 3.0.2)
- Affected
- older than 3.0.2
- Fixed in
- 3.0.2
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Builderall for WordPress plugin before 3.0.2 does not bind the state value of its public OAuth authentication routes to the initiating user session, allowing unauthenticated attackers to complete the connection flow and overwrite the stored third-party integration access token. A durable overwrite requires the site to already be connected to a paid account.
critical 9.9 CVE-2026-22390 · published 2026-03-05
Remote code execution in Builderall for WordPress (3.0.1 and older)
- Affected
- 3.0.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Control of Generation of Code ('Code Injection') vulnerability in Builderall Builderall Builder for WordPress builderall-cheetah-for-wp allows Code Injection.This issue affects Builderall Builder for WordPress: from n/a through <= 3.0.1.
medium 6.5 CVE-2025-62987 · published 2025-10-27
Stored cross-site scripting (XSS) in Builderall for WordPress (3.0.1 and older)
- Affected
- 3.0.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Builderall Builderall Builder for WordPress builderall-cheetah-for-wp allows Stored XSS.This issue affects Builderall Builder for WordPress: from n/a through <= 3.0.1.
medium 4.9 CVE-2024-30532 · published 2024-04-02
Server-side request forgery (SSRF) in Builderall for WordPress (2.0.1 and older)
- Affected
- 2.0.1 and older
- Fixed in
- 2.0.2
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Server-Side Request Forgery (SSRF) vulnerability in Builderall Team Builderall Builder for WordPress.This issue affects Builderall Builder for WordPress: from n/a through 2.0.1.
Recent activity
- 2026-08-19 — closed on wordpress.org (Security Issue).
- 2026-09-10 — Stored cross-site scripting (XSS) disclosed (CVE-2026-15820), fix version not stated.
- 2026-09-10 — Missing authorization check disclosed (CVE-2026-15823), fix version not stated.
- 2026-09-10 — Stored cross-site scripting (XSS) disclosed (CVE-2026-15796), fix version not stated.
Get an email when Builderall for WordPress has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Builderall for WordPress (builderall-cheetah-for-wp) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (3) · Missing authorization (2) · Remote code execution (1) · Server-side request forgery (SSRF) (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/builderall-cheetah-for-wp (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/builderall-cheetah-for-wp"><img src="https://laskyr.com/plugins/builderall-cheetah-for-wp/badge.svg" alt="Builderall for WordPress vulnerability status"></a>