LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35774: WordPress LWS Tools Plugin <= 2.4.1 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in LWS LWS Tools plugin <= 2.4.1 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-35774 is a cross-site request forgery issue in the WordPress LWS Tools plugin through version 2.4.1. A successful attack would require a victim to interact with attacker-controlled content while logged in, potentially causing unintended changes. The public sources rate impact as medium, not catastrophic.

Executive priority

Treat this as a routine but real WordPress plugin risk. Prioritize internet-facing business sites using LWS Tools, especially where administrators frequently manage content. It does not warrant emergency response based on the supplied evidence.

Technical view

The CVE describes multiple CSRF weaknesses in LWS Tools <= 2.4.1 for WordPress. CVSS 3.1 is 5.4 with network access, low complexity, no attacker privileges, and required user interaction. Reported impact is low integrity and availability, with no confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress sites running the LWS Tools plugin at version 2.4.1 or earlier. Sites not using the plugin are not exposed by this CVE. The source bundle does not identify specific vulnerable endpoints or configurations.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not state active exploitation. Exploitation depends on social engineering or browser interaction by a logged-in user with sufficient privileges to trigger the affected plugin behavior.

Researcher notes

The public bundle gives vulnerability class, product, version boundary, CVSS, and one Patchstack reference, but not affected actions, endpoint names, exploit details, or a named fixed version. Avoid assuming exploitability beyond CSRF requiring user interaction.

Mitigation direction

  • Inventory WordPress sites for the LWS Tools plugin and recorded version.
  • Check LWS or Patchstack guidance for a fixed version or official workaround.
  • Update the plugin if vendor guidance confirms a patched release.
  • Disable the plugin where business impact is acceptable until guidance is verified.
  • Reinforce admin anti-phishing controls and avoid browsing untrusted links while authenticated.

Validation and detection

  • Confirm whether LWS Tools is installed on each WordPress site.
  • Record plugin versions and flag version 2.4.1 or earlier for review.
  • Check vendor release notes for CSRF-related fixes after 2.4.1.
  • Review WordPress admin logs for unexpected plugin setting changes.
  • Verify remediation by confirming the installed plugin version or removal status.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-35774 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-35774Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LWSLWS Toolslws-tools, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.