dbcve.org
Lws ToolsWordPress extension · Lws

CVE-2023-35774

HIGH · 8.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 2.4.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in LWS LWS Tools plugin <= 2.4.1 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the LWS LWS Tools WordPress plugin versions 2.4.1 and below allows attackers to trick authenticated users into unknowingly submitting malicious requests to the plugin, potentially performing unauthorized actions.

MitigationImplement anti-CSRF tokens (nonces) in all state-changing forms and AJAX actions within the plugin, and validate these tokens on the server side before processing any requests.

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
Lws ToolsWordPress extension
Affected:< 2.4.2

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 LWS LWS Tools plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'LWS Tools' or 'Lws Lws Tools', or inspect the plugin directory /wp-content/plugins/ for a folder starting with 'lws-'.
    Affected if The plugin is not installed.
  2. Check the installed plugin version
    In WordPress admin Plugins list, click on the plugin name to view details, or open the main plugin file (usually lws-tools.php or similar) and look for the 'Version' header in the plugin comments.
    Affected if Version is 2.4.1 or below.
  3. Identify state-changing forms and AJAX actions
    Inspect the plugin source code for HTML form tags (<form) and AJAX endpoints (admin-ajax.php calls, wp_ajax_ hooks) that perform actions like settings saves, user data modifications, or configuration changes.
    Affected if The plugin contains forms or AJAX actions that process requests without anti-CSRF token validation.
  4. Verify CSRF token presence in forms
    Search the plugin PHP files for 'wp_nonce_field', 'wp_nonce_url', or 'check_admin_referer' calls around form handling code. Check if each form that changes state includes a nonce field.
    Affected if Forms exist that do not generate or validate CSRF tokens (nonces) before processing submissions.
  5. Verify CSRF token presence in AJAX actions
    Search the plugin PHP files for AJAX handlers (functions hooked to wp_ajax_) and check if they call 'check_ajax_referer' or 'wp_verify_nonce' before processing requests.
    Affected if AJAX actions exist that process requests without verifying CSRF tokens.

The environment is affected if the LWS LWS Tools plugin is installed with version 2.4.1 or below AND contains forms or AJAX actions that process state-changing requests without validating anti-CSRF nonces.

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 2.4.2 or later
Fixed in 2.4.2
Interim mitigation

Implement anti-CSRF tokens (nonces) in all state-changing forms and AJAX actions within the plugin, and validate these tokens on the server side before processing any requests.

Recommended fix Moderate confidence

LWS Tools version 2.4.2

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the LWS Tools plugin
  4. Check if an update is available
  5. If update available, click 'Update Now' to update to version 2.4.2 or later
  6. Verify the plugin is updated to version 2.4.2 or higher after the update completes

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

Fix this in Lws Tools Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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