Page Builder SandwichWordPress extension · Pagebuildersandwich
CVE-2024-1285
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 Page Builder Sandwich – Front End WordPress Page Builder Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'gambit_builder_save_content' function in all versions up to, and including, 5.1.0. This makes it possible for authenticated attackers, with subscriber access and above, to insert arbitrary content into existing posts.
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 Page Builder Sandwich WordPress plugin fails to enforce authorization checks on the 'gambit_builder_save_content' function, allowing any authenticated user with subscriber-level privileges or higher to modify content in existing posts. This IDOR-style vulnerability permits unauthorized insertion of arbitrary content into pages without proper capability validation.
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
Page Builder SandwichWordPress extension
<= 5.1.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 plugin is installedCheck your WordPress plugins directory for 'pagebuildersandwich' or 'Page Builder Sandwich' folder, typically at wp-content/plugins/Affected if The plugin folder exists in the WordPress installation
-
Check installed versionRead the main plugin file (usually index.php or main php file) inside the plugin folder to find the 'Version:' header, or query via WP CLI: wp plugin list --name='pagebuildersandwich'Affected if Version is 5.1.0 or lower (or version header cannot be read)
-
Confirm vulnerable function existsSearch plugin source files for the function 'gambit_builder_save_content' - check PHP files in the plugin folder for this function definition or action hookAffected if The function 'gambit_builder_save_content' is defined or hooked without a current_user_can() capability check before it
-
Check for subscriber-level usersIn WordPress admin, go to Users > All Users and review user roles. Subscribers have minimal privileges by default.Affected if Any user account exists with 'Subscriber' role or any authenticated user can access the site
If the Page Builder Sandwich plugin version is 5.1.0 or below AND the gambit_builder_save_content function exists without capability checks, your environment is affected by CVE-2024-1285.
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.
From vendor dataUpdate to plugin version 5.1.1 or later which implements proper capability checks, or implement a custom capability check (e.g., current_user_can('edit_posts')) before executing the save function.
Fix this in Page Builder Sandwich
Scoped from the published advisory
- 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-1285 — 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-1285 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