Unlimited Addons For Wpbakery Page BuilderWordPress extension · Unitecms
CVE-2023-6925
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 Unlimited Addons for WPBakery Page Builder plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation on the 'importZipFile' function in versions up to, and including, 1.0.42. This makes it possible for authenticated attackers with a role that the administrator previously granted access to the plugin (the default is editor role, but access can also be granted to contributor role), to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 Unlimited Addons for WPBakery Page Builder plugin for WordPress versions up to 1.0.42 contains an arbitrary file upload vulnerability in the importZipFile function. Due to insufficient file type validation, authenticated users with editor-level access (or contributor if granted by administrator) can upload arbitrary files including malicious PHP scripts, leading to potential 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
Unlimited Addons For Wpbakery Page BuilderWordPress extension
<= 1.0.42CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify if the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Unitecms Unlimited Addons For Wpbakery Page Builder' or check the plugin directory /wp-content/plugins/ for a folder containing 'unlimited-addons' or similar naming. Alternatively, check the plugin's main PHP file header for the version number.Affected if The plugin is found installed on the WordPress site.
-
Determine the installed versionCheck the plugin's main PHP file (usually in /wp-content/plugins/[plugin-folder]/unite_addons.php or similar) for the 'Version' header in the plugin comment block, or access it via Plugins page in WordPress admin where version is displayed.Affected if The version number displayed is 1.0.42 or lower.
-
Check for the vulnerable import function exposureExamine the plugin files for the importZipFile function. Look in files named import.php, unzip.php, or similar within the plugin folder. Check if the function is accessible without additional nonce verification or capability checks beyond basic authentication.Affected if The importZipFile function exists and lacks proper file type validation (allows .php uploads).
-
Audit uploaded files for suspicious contentSearch the /wp-content/uploads/ directory for recently uploaded .php files, .zip files, or files with double extensions (e.g., image.php.jpg). Check file creation dates against the timeframe the plugin was active.Affected if Unexpected .php files or other executable files are found in the uploads directory, especially if they were uploaded by users with editor-level or contributor access.
The environment is affected if the Unitecms Unlimited Addons For WPBakery Page Builder plugin version is 1.0.42 or lower, as this version contains the vulnerable importZipFile function that allows authenticated editors/contributors to upload arbitrary files.
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 the plugin to version 1.0.43 or later which patches the file validation vulnerability. If no update is available, disable and remove the plugin until a fix is released.
Fix this in Unlimited Addons For Wpbakery Page Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6925 — 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-2023-6925 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