dbcve.org
BorderlessWordPress extension · Visualmodo

CVE-2024-10867

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-31
Fix available
A fix is available. Upgrade to 1.6.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Borderless – Widgets, Elements, Templates and Toolkit for Elementor & Gutenberg plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 1.6.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

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 Borderless WordPress plugin fails to properly sanitize SVG file uploads and escape output when serving these files. Authenticated users with Author-level permissions can upload SVG files containing malicious JavaScript payloads that execute in the browsers of users who access those files, creating a stored XSS vulnerability.

MitigationUpdate the plugin to the latest patched version when available. Until then, disable SVG uploads via plugin settings or server configuration, and audit existing media library uploads for suspicious SVG files.

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
BorderlessWordPress extension
Affected:< 1.6.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Identify if Borderless plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Borderless' by Visualmodo, or check the /wp-content/plugins/ directory for a borderless folder. Check the plugin version listed in the plugin header.
    Affected if The Borderless plugin is installed and the version is below 1.6.0
  2. Check for SVG file uploads in media library
    In WordPress admin, go to Media > Library and filter or search for .svg files. Alternatively, query the wp_posts table in the database for posts with post_type='attachment' and guid ending in .svg.
    Affected if SVG files exist in the media library, as these could contain malicious payloads if uploaded by a compromised Author-level account
  3. Verify if Author-level users exist
    In WordPress admin, go to Users and review user roles. Authors have the capability to upload files. Check the wp_usermeta table for users with meta_key='wp_capabilities' containing 'author'.
    Affected if Any user account with Author role exists, as they have permission to upload files including SVG
  4. Confirm SVG upload is not restricted
    Check the Borderless plugin settings in WordPress admin under Borderless > Settings or similar. Look for any SVG uploadallow/disable toggle. Also check if the plugin file includes SVG handling code in borderless.php or related files.
    Affected if SVG uploads are enabled in the plugin configuration, allowing the exploit pathway

A user is affected if the Borderless plugin version is below 1.6.0, SVG uploads are enabled in the plugin, and Author-level user accounts exist who could have uploaded malicious SVG files to the media library.

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
Upgrade available Upgrade to 1.6.0 or later
Fixed in 1.6.0
Interim mitigation

Update the plugin to the latest patched version when available. Until then, disable SVG uploads via plugin settings or server configuration, and audit existing media library uploads for suspicious SVG files.

Recommended fix High confidence

Borderless plugin version 1.6.0 or later

  1. 1. Log in to the WordPress admin dashboard with an account that has Administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'Borderless – Widgets, Elements, Templates and Toolkit for Elementor & Gutenberg' plugin.
  4. 4. If an update is available, click 'Update Now' to update the plugin to the latest version.
  5. 5. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is running version 1.6.0 or higher.
  7. 7. Confirm the vulnerability is remediated by testing that SVG file uploads are properly sanitized.

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

Fix this in Borderless Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10867 — 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-2024-10867 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