CVE-2021-4332
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 Plus Addons for Elementor plugin for WordPress is vulnerable to arbitrary file reads in versions up to, and including 4.1.9 (pro) and 2.0.6 (free). The plugin has a feature to add an "Info Box" to an Elementor created page. This Info Box can include an SVG image for the box. Unfortunately, the plugin used file_get_contents with no verification that the file being supplied was an SVG file, so any user with access to the Elementor page builder, such as contributors, could read arbitrary files on the WordPress installation.
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 Plus Addons for Elementor plugin has an arbitrary file read vulnerability in its Info Box feature. The plugin uses file_get_contents() to load SVG images without validating that the requested file is actually an SVG, allowing authenticated users with Elementor page builder access (contributors and above) to read any accessible file on the server.
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.0.6<= 4.1.9CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins. Look for 'The Plus Addons For Elementor' (free) or 'The Plus Addons For Elementor Pro'. Note the installed version number shown.Affected if The plugin is installed and version is 2.0.6 or lower for free, or 4.1.9 or lower for pro.
-
Determine if Elementor builder access is open to low-privileged usersGo to Users > All Users in WordPress admin. Check which users have access to the Elementor page editor. Typically, Contributor role and above can access Elementor if enabled in User Roles settings under The Plus Addons settings.Affected if Users with Contributor, Author, or Editor roles have permission to use Elementor page builder.
-
Identify if Info Box widget is in useSearch your WordPress content for pages or posts edited with Elementor that include the Info Box widget. In Elementor editor, search 'Info Box' in the widget panel. Check existing pages by viewing source for elements containing 'theplus-info-box' or similar class names.Affected if Any page or post uses the Info Box widget from this plugin.
-
Verify the vulnerable file read endpoint existsAttempt to access a known vulnerable endpoint pattern such as /wp-admin/admin-ajax.php?action=theplus_get_post_by_id&post_id=../../wp-config. If the response contains file contents or displays an error related to file access, the endpoint is reachable.Affected if The endpoint responds and allows reading files outside the intended SVG directory.
A user is affected if the Plus Addons for Elementor plugin is installed at version 2.0.6 or below (free) or 4.1.9 or below (pro), and the Info Box widget is accessible to users with Contributor-level access or higher.
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 · scopedUpgrade to version 4.1.10 (pro) or 2.0.7 (free) which adds proper file type validation, or restrict Elementor builder access to trusted users only until the patch can be applied.
Free: > 2.0.6; Pro: > 4.1.9 (upgrade to latest available version from WordPress plugin repository or vendor)
- 1. Update The Plus Addons For Elementor (free version) to the latest available version from the WordPress plugin repository
- 2. Update The Plus Addons For Elementor Pro to the latest available version from the vendor (if using the pro version)
- 3. Verify the update was successful by checking the plugin version number
- 4. Confirm that contributor-level users can no longer use the Info Box SVG feature to read arbitrary files
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-4332 — 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-4332 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