dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-1793

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Element Pack Addons for Elementor plugin for WordPress is vulnerable to arbitrary file reads in all versions up to, and including, 8.3.17 via the SVG widget and a lack of sufficient file validation in the 'render_svg' function. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

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 confidence

The Element Pack Addons plugin for WordPress versions up to 8.3.17 contain an arbitrary file read vulnerability in the SVG widget. The render_svg function lacks sufficient validation on file paths, allowing authenticated users with contributor-level access or higher to read arbitrary server files by manipulating file paths in the widget.

MitigationUpdate the Element Pack Addons plugin to version 8.3.18 or later. If immediate update is not possible, restrict contributor-level user permissions and disable the SVG widget until a patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Element Pack Addons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Element Pack Addons' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active in WordPress.
  2. Determine the installed plugin version
    In the Plugins list, click on the plugin name to view details, or inspect the plugin header in /wp-content/plugins/bdthemes-element-pack-lite/ or /wp-content/plugins/bdthemes-element-pack/ for the Version: x.x.x field.
    Affected if The version number is 8.3.17 or lower.
  3. Identify active user accounts with contributor-level access
    In WordPress admin, go to Users and review the role assigned to each user. Contributors, Authors, Editors, and Administrators all have contributor-level access or higher.
    Affected if There is at least one user account with the Contributor, Author, Editor, or Administrator role.
  4. Check for usage of the SVG widget in pages or templates
    Review published pages, posts, or custom post types that may contain the Element Pack SVG widget. In the WordPress block editor or page builder, search for any widget or block named 'SVG' or 'Element Pack SVG' that is placed on a live page.
    Affected if The SVG widget from Element Pack is currently placed on any published content.

A user is affected if the Element Pack Addons plugin is active at version 8.3.17 or lower, the SVG widget is in use, and at least one contributor-level or higher user account exists on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Element Pack Addons plugin to version 8.3.18 or later. If immediate update is not possible, restrict contributor-level user permissions and disable the SVG widget until a patch can be applied.

Recommended fix Moderate confidence

Latest version higher than 8.3.17 (check wordpress.org/plugins/bdthemes-element-pack/ for current stable release)

  1. 1. Log in to WordPress admin dashboard with contributor-level or higher privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Element Pack Addons for Elementor' in the plugin list
  4. 4. Check the current installed version (should be 8.3.17 or below if vulnerable)
  5. 5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/bdthemes-element-pack/
  6. 6. After updating, verify the new version number reflects the fix (version higher than 8.3.17)
  7. 7. Test the SVG widget functionality to ensure the path traversal vulnerability is patched and the widget still works correctly
Caveat Minor: Review Element Pack settings after upgrade as minor UI/function changes may occur; test SVG widget thoroughly before production use

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1793 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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