CVE-2021-38346
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 Brizy Page Builder plugin <= 2.3.11 for WordPress allowed authenticated users to upload executable files to a location of their choice using the brizy_create_block_screenshot AJAX action. The file would be named using the id parameter, which could be prepended with "../" to perform directory traversal, and the file contents were populated via the ibsf parameter, which would be base64-decoded and written to the file. While the plugin added a .jpg extension to all uploaded filenames, a double extension attack was still possible, e.g. a file named shell.php would be saved as shell.php.jpg, and would be executable on a number of common configurations.
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 Brizy Page Builder plugin <= 2.3.11 for WordPress has an authenticated arbitrary file upload vulnerability via the brizy_create_block_screenshot AJAX action. Authenticated users can control the filename via the id parameter (including directory traversal with '../') and the file contents via the ibsf parameter (base64-decoded). Although the plugin appends .jpg to filenames, double extension attacks (e.g., shell.php.jpg) allow execution on common server configurations.
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<= 2.3.11CVSS 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 Brizy Page Builder plugin is installedCheck for the Brizy plugin directory in wp-content/plugins/ or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if Brizy Page Builder appears in the list of installed plugins
-
Determine installed Brizy plugin versionRead the main plugin file (typically brizy/brizy.php) and look for the 'Version' header in the plugin comments, or check the version column in WordPress admin Plugins pageAffected if The version listed is 2.3.11 or lower
-
Confirm AJAX action is accessible to non-admin usersTest if the brizy_create_block_screenshot AJAX action responds to authenticated requests from editor, author, or subscriber role users by inspecting user capabilities or testing with a low-privilege accountAffected if Users with roles below Administrator can access and execute the brizy_create_block_screenshot AJAX action
-
Inspect uploads directory for suspicious filesExamine wp-content/uploads/ and subdirectories for files with double extensions (e.g., shell.php.jpg, malware.jpg) or PHP files in upload folders that should only contain imagesAffected if Unexpected PHP files or double-extension files are present in upload directories
-
Check server configuration for double extension handlingReview server configuration (Apache .htaccess, Nginx config) to see if .jpg files in upload directories are configured to be handled as PHP (AddHandler or similar directives)Affected if Server is configured to execute files with .jpg extension as PHP scripts
You are affected if Brizy Page Builder version 2.3.11 or lower is installed AND non-administrator authenticated users can access the brizy_create_block_screenshot AJAX action AND either suspicious files exist in uploads or the server executes double-extension files as PHP.
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 Brizy Page Builder plugin to version 2.3.12 or later. If immediate updating is not possible, disable the brizy_create_block_screenshot AJAX action or restrict access to authenticated administrators only.
Brizy Page Builder version 2.3.12 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find Brizy Page Builder in the plugin list
- Check if an update is available (version should be higher than 2.3.11)
- If update available, click 'Update Now' to install the patched version
- Verify the update was successful by checking the plugin version after updating
- If no update appears, manually download the latest version from wordpress.org or the Brizy official website and upload via Plugins > Add New > Upload Plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38346 — 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-2021-38346 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