dbcve.org
BorderlessWordPress extension · Visualmodo

CVE-2024-34757

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 1.5.4 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Visualmodo Borderless borderless allows DOM-Based XSS.This issue affects Borderless: from n/a through <= 1.7.3.

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

DOM-based Cross-site Scripting (XSS) vulnerability in Visualmodo Borderless WordPress theme. The theme improperly neutralizes user input during web page generation, allowing attackers to inject malicious JavaScript into pages viewed by other users.

MitigationUpdate Borderless theme to latest version after vendor patch release, or implement proper output encoding/escaping for all user-supplied data in JavaScript code and HTML contexts.

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.5.4

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. Locate Borderless theme installation
    Access the WordPress theme directory (wp-content/themes/) and check for a folder named 'borderless' or 'visualmodo-borderless'. Alternatively, log into WordPress admin and navigate to Appearance > Themes to confirm the Borderless theme is installed.
    Affected if The Borderless theme folder exists in the themes directory or is listed in WordPress admin theme list.
  2. Identify installed theme version
    Open the theme's main style.css file located at wp-content/themes/borderless/style.css (or the equivalent folder name) and locate the 'Version:' header in the file comments at the top. Alternatively, check the theme details panel in WordPress admin (Appearance > Themes > Borderless Theme Details).
    Affected if The version number cannot be determined or the theme is present without a clear version declaration.
  3. Compare version to affected range
    Compare the identified version number to the affected range: versions prior to 1.5.4 are vulnerable. For example, versions 1.0.0 through 1.5.3 are all affected.
    Affected if The installed version is lower than 1.5.4 (e.g., 1.5.3, 1.4.0, 1.0.5, etc.).

Your environment is affected if the Visualmodo Borderless theme is installed and its version is less than 1.5.4.

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.5.4 or later
Fixed in 1.5.4
Interim mitigation

Update Borderless theme to latest version after vendor patch release, or implement proper output encoding/escaping for all user-supplied data in JavaScript code and HTML contexts.

Recommended fix Moderate confidence

Borderless version 1.5.4 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Dashboard > Appearance > Themes in WordPress admin.
  3. 3. If you have shell/FTP access, download the latest version of Borderless theme (version 1.5.4 or later) from a trusted source such as the official Visualmodo website or WordPress theme repository.
  4. 4. Update the Borderless theme to version 1.5.4 or newer.
  5. 5. Verify the update was successful by checking the theme version in Appearance > Themes.
  6. 6. Test affected functionality to ensure the XSS vulnerability is remediated and the site functions correctly.
Caveat Review theme customizations and child theme compatibility after upgrade, as minor version updates may include template changes

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

Fix this in Borderless Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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