Skip to main content

Do Lasso CVE-2026-28157

| EUVDEUVD-2026-57950 HIGH
Path Traversal: '.../...//' (CWE-35)
2026-08-13 Patchstack GHSA-36hp-4q45-jxjc
7.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Register or obtain subscriber account
  2. Delivery
    Authenticate to WordPress site
  3. Exploit
    Send crafted HTTP request to Do Lasso endpoint
  4. Install
    Inject path traversal sequence in filename parameter
  5. C2
    Escape plugin directory boundary
  6. Execute
    Read or overwrite arbitrary server files
  7. Impact
    Achieve credential theft or persistent access

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path traversal prevention
Exploitation Conditions

Exploitation requires an authenticated WordPress account with at minimum subscriber-level privileges on the target site - the lowest WordPress role, granted to any registered user. This means the attack surface is limited to sites where user registration is enabled (Settings > General > Anyone can register) or where the attacker has otherwise legitimately or illegitimately obtained subscriber credentials. The CVSS AC:H rating indicates additional complexity, which may correspond to a requirement to know or enumerate specific file paths on the server, or to craft a precisely structured request. Sites with closed registration where all subscriber accounts belong to trusted users face substantially reduced risk. The vulnerability does not require administrative or editor access, and no specific plugin feature toggle or non-default configuration beyond the plugin being active is described in available data.

Impact

The CVSS 3.1 base score of 7.5 reflects high CIA impact but is moderated by Attack Complexity: High and Privileges Required: Low (subscriber-level authentication). This positions the vulnerability as exploitable only by registered WordPress users - not anonymous visitors - which meaningfully limits the exposed attack surface on sites that do not allow open registration. The AC:H rating indicates exploitation is not straightforward and may require specific conditions such as knowledge of target file paths or a particular request structure. No EPSS data was provided in the intelligence feed, limiting probabilistic exploitation forecasting. There is no CISA KEV listing and no reported POC, suggesting no confirmed active exploitation at time of analysis. Despite the high base score, the real-world priority is primarily elevated for WordPress sites with open user registration or where subscriber accounts may be held by untrusted third parties. Sites with closed registration where all users are trusted face substantially lower practical risk.

Exploit ScenarioDerived

An attacker registers a free account on a WordPress site running Do Lasso <= 358 with open user registration enabled, then authenticates as a subscriber and sends a crafted HTTP request to a plugin endpoint with a manipulated file path parameter containing traversal sequences. By escaping the plugin's intended directory boundary, the attacker reads sensitive server files such as wp-config.php (exposing database credentials) or overwrites WordPress core or plugin files to achieve persistent code execution. No public exploit code has been identified at time of analysis, but the Patchstack disclosure provides sufficient vulnerability class detail for skilled researchers to develop one.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 13, 2026

Path traversal in the Do Lasso WordPress plugin (versions <= 358) allows authenticated subscribers to traverse the server file system beyond the intended directory scope, achieving high confidentiality, integrity, and availability impact. The vulnerability is exploitable by any authenticated WordPress user holding the subscriber role - the lowest privilege tier - over the network, making it accessible to any registered site user. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, but the Patchstack advisory signals a patched version is available.

RemediationAI

Update the Do Lasso plugin to a version above 358 through the WordPress admin dashboard or wp-cli (wp plugin update lasso). The Patchstack advisory at https://patchstack.com/database/wordpress/plugin/lasso/vulnerability/wordpress-do-lasso-plugin-358-path-traversal-vulnerability should be consulted to confirm the exact patched release version, as the specific fix version was not independently confirmed in the available data. If immediate patching is not possible, disable open user registration to prevent untrusted parties from obtaining subscriber-level accounts, thereby removing the PR:L attack surface. Additionally, consider using a Web Application Firewall (WAF) rule to block requests containing path traversal sequences (../, ..\ encoded variants) directed at plugin endpoints, though this may risk false positives on legitimate file-handling features. Deactivating the plugin entirely is the most effective compensating control if affiliate link functionality can be temporarily suspended.

Affected VersionsENISA

Do Lasso n/a ≤358

Affected Packages

euvd do_lasso no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Do Lasso (CPE: cpe:2.3:a:lasso_analytics,_inc.:do_lasso:*:*:*:*:*:*:*:*) is a WordPress affiliate link management plugin developed by Lasso Analytics, Inc. The flaw is classified as CWE-35 (Path Traversal), a root-cause class in which user-controlled input is used to construct file system paths without sufficient canonicalization or boundary enforcement, permitting directory escape via sequences such as '../'. In a WordPress context, path traversal vulnerabilities in plugins typically manifest in file-serving, import/export, or template-rendering endpoints that accept filenames or paths as parameters. Because the CVSS vector reflects High impact across all three CIA pillars, the affected endpoint likely permits both file read (C:H) and file write or deletion (I:H, A:H), suggesting the traversal is not read-only.

Know when Do Lasso gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.5 HIGH

Network-exploitable by authenticated subscribers (PR:L); AC:H reflects path enumeration complexity; S:U as impact stays within WordPress application boundary.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Subscriber Path Traversal in Do Lasso <= 358 versions.

Executive ViewAI

Why It Matters

Do Lasso WordPress plugin versions 358 and below contain a path traversal vulnerability allowing any registered website subscriber to access and manipulate arbitrary server files, exposing database credentials, configuration files, and other sensitive assets to compromise. This creates substantial risk of data theft and website compromise for any organization running this plugin on WordPress sites with open registration.

Business Impact: High
Compensating Controls

Apply vendor patch. If patch deployment is delayed: immediately disable the Do Lasso plugin, restrict subscriber role assignments to essential personnel only, implement Web Application Firewall rules to block path traversal patterns, enable and monitor server file access logs for exploitation attempts, and consider file integrity monitoring on sensitive system directories.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Prevalence
Medium
popular WordPress affiliate link management plugin with niche but meaningful install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy