Essential Addons For ElementorWordPress extension · Wpdeveloper
CVE-2022-0320
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 Essential Addons for Elementor WordPress plugin before 5.0.5 does not validate and sanitise some template data before it them in include statements, which could allow unauthenticated attackers to perform Local File Inclusion attack and read arbitrary files on the server, this could also lead to RCE via user uploaded files or other LFI to RCE techniques.
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 Essential Addons for Elementor plugin before version 5.0.5 fails to validate and sanitize template data before using it in PHP include statements, enabling unauthenticated attackers to perform Local File Inclusion (LFI) attacks. This allows reading arbitrary files on the server and can be escalated to Remote Code Execution (RCE) through user-uploaded files or LFI-to-RCE techniques.
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
Essential Addons For ElementorWordPress extension
< 5.0.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Essential Addons for Elementor is installedCheck the WordPress plugins directory or access wp-admin > Plugins to confirm Essential Addons for Elementor is present and activeAffected if The plugin is installed and active on the WordPress site
-
Check installed version numberLocate the plugin main file (typically essential-addons-for-elementor.php) and find the Version header in the plugin comments, or check via wp-admin > Plugins > Plugin DetailsAffected if The version is below 5.0.5 (e.g., 5.0.4, 5.0.3, etc.)
-
Identify vulnerable template include codeExamine the plugin files for PHP include/require statements using unsanitized template variables (look for patterns like 'include($template)' or 'require($path)' without proper validation in the includes/template-handler files)Affected if The plugin contains template include code that uses user-controllable input without validation
-
Check web server logs for suspicious include requestsReview server access logs (Apache/Nginx error and access logs) for patterns like '../' or '/etc/passwd' in query parameters targeting the plugin endpointsAffected if Logs show LFI attempt patterns (directory traversal sequences) hitting the plugin URL endpoints
You are affected if Essential Addons for Elementor is installed with a version lower than 5.0.5 and the vulnerable template include functionality is accessible.
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 · scoped5.0.5
Update Essential Addons for Elementor to version 5.0.5 or later immediately, as the vulnerability can be exploited without authentication. Additionally, audit logs for indicators of compromise and consider whether server-side access may have been achieved.
Essential Addons for Elementor version 5.0.5 or later
- Backup the WordPress site database and files before making any changes
- Update the Essential Addons for Elementor plugin to version 5.0.5 or later through the WordPress admin dashboard (Plugins > Updates or directly from the plugin page)
- Verify the updated version is 5.0.5 or higher in the installed plugins list
- Confirm the plugin functions correctly on the website front-end and back-end
- Review server logs for any suspicious access attempts targeting the vulnerable endpoint
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Essential Addons For Elementor
Scoped from the published advisory
- 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-2022-0320 — 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-2022-0320 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