LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45047: WordPress LeadSquared Suite Plugin <= 0.7.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in LeadSquared, Inc LeadSquared Suite plugin <= 0.7.4 versions.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress LeadSquared Suite plugin through version 0.7.4. A malicious site could trick a logged-in WordPress user into unintentionally changing plugin state, reportedly leading to form deactivation. Business impact is mainly disruption to lead capture forms rather than data theft, based on the supplied CVSS vector.

Executive priority

Prioritize this for any WordPress site where LeadSquared forms support revenue, marketing, or customer intake. The main concern is interruption of lead capture, not confirmed data compromise. Treat patch or vendor guidance review as time-sensitive for affected sites.

Technical view

CVE-2023-45047 is a CWE-352 CSRF issue in LeadSquared Suite for WordPress, package leadsquared-suite, versions <=0.7.4. The CVSS 3.1 score is 7.1 with network attack vector, low complexity, no privileges, required user interaction, low integrity impact, and high availability impact.

Likely exposure

Exposure is limited to WordPress installations that have the LeadSquared Suite plugin installed at version 0.7.4 or earlier. Sites without this plugin are not affected by the supplied evidence.

Exploitation context

The supplied sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation would require user interaction, likely involving a logged-in WordPress user being induced to perform an unintended browser request.

Researcher notes

Evidence is limited to CVE metadata and Patchstack’s vulnerability entry. The source bundle identifies CSRF leading to form deactivation but does not provide a fixed version, exploit status, or detailed vulnerable endpoint information. Avoid assuming broader impact without vendor confirmation.

Mitigation direction

  • Inventory WordPress sites for the leadsquared-suite plugin and installed version.
  • Check LeadSquared or Patchstack guidance for a fixed version or vendor mitigation.
  • Remove or disable the plugin where it is not business-critical.
  • Review access controls for users who can administer plugin forms.
  • Monitor for unexpected form deactivation or lead-capture disruption.

Validation and detection

  • Confirm whether leadsquared-suite is installed on each WordPress site.
  • Verify whether any installed version is 0.7.4 or earlier.
  • Review WordPress audit logs for unexpected plugin or form configuration changes.
  • Test that lead capture forms remain active and functioning.
  • Document business owners for affected LeadSquared integrations.
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-45047 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
High
CVSS
7.1 (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:H

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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H2.84.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-45047Attack 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:H

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
LeadSquared, IncLeadSquared Suiteleadsquared-suite, 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.