dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57337

HIGH · 7.1 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 7 weeks old

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
Unauthenticated Cross Site Scripting (XSS) in Landing Page Builder <= 1.5.3.5 versions.

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

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in the Landing Page Builder WordPress plugin versions 1.5.3.5 and prior. The flaw allows remote attackers to inject malicious JavaScript code into landing pages without authentication, potentially leading to session hijacking, credential theft, or malware distribution against site visitors.

MitigationUpdate the Landing Page Builder plugin to the latest version immediately. If no update is available, temporarily disable the plugin or implement Web Application Firewall (WAF) rules to block XSS attack patterns until a patch is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 the Landing Page Builder plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Landing Page Builder' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In the Plugins list, click on the plugin to view its details, or inspect the plugin main file header for the 'Version' comment. Compare the version number to 1.5.3.5.
    Affected if The installed version is 1.5.3.5 or any version prior to it (for example: 1.5.3.4, 1.5.3, 1.5.2, 1.5.1, etc.)
  3. Confirm the plugin is active
    In the WordPress Plugins list, verify whether the Landing Page Builder plugin shows as 'Active' under the plugin status column.
    Affected if The plugin is currently activated on the WordPress site
  4. Inspect landing pages for injected scripts
    View the source code of published landing pages created by the plugin. Look for unexpected script tags, script src attributes pointing to unfamiliar domains, or inline JavaScript events (onclick, onload, onerror) that were not intentionally added.
    Affected if Any unknown or malicious JavaScript code is present in the landing page source
  5. Review server access logs for XSS attack indicators
    Examine web server access logs (Apache, Nginx, or WordPress debug logs) for GET/POST requests to landing page URLs containing patterns like <script, javascript:, or %3Cscript in the query parameters or POST body.
    Affected if Suspicious requests containing XSS payload patterns are found in the logs targeting landing pages

The environment is affected if the Landing Page Builder plugin is installed, active, and running version 1.5.3.5 or prior.

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 Landing Page Builder plugin to the latest version immediately. If no update is available, temporarily disable the plugin or implement Web Application Firewall (WAF) rules to block XSS attack patterns until a patch is released.

Recommended fix Moderate confidence

Any version of Landing Page Builder newer than 1.5.3.5 (check WordPress plugin repository for latest release)

  1. 1. Identify the WordPress plugin 'Landing Page Builder' in your WordPress installation
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Landing Page Builder plugin and check its current version
  4. 4. If the installed version is 1.5.3.5 or lower, update the plugin to the latest available version
  5. 5. After updating, verify the plugin version has been incremented beyond 1.5.3.5
  6. 6. Test the plugin functionality to ensure the update did not break existing landing pages
  7. 7. Clear any website caches if you use caching plugins
Caveat Verify compatibility with your WordPress version and other plugins after updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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