LiveActive security incident?Get immediate response
CVE Record

CVE-2022-47172: WordPress WooLentor Plugin <= 2.6.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in HasThemes ShopLentor plugin <= 2.6.2 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-47172 is a CSRF issue in the HasThemes ShopLentor/WooLentor WordPress plugin up to 2.6.2. An attacker could potentially trick a logged-in user into triggering unintended plugin actions. The cited data shows limited integrity impact, not data theft or outage.

Executive priority

Treat as a routine but real WordPress hygiene issue. It is not marked as actively exploited, and impact is limited, but affected ecommerce or lead-generation sites should be updated promptly because CSRF can enable unauthorized configuration changes through trusted users.

Technical view

The source describes CWE-352 Cross-Site Request Forgery in the woolentor-addons package, affecting ShopLentor/WooLentor versions up to 2.6.2. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites running the HasThemes ShopLentor/WooLentor plugin, package woolentor-addons, at version 2.6.2 or earlier. Sites without this plugin are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The CVSS vector requires user interaction, consistent with CSRF: a logged-in user must be induced to make an unintended request. No exploit details or exploited-in-the-wild evidence are provided.

Researcher notes

The public bundle does not identify the exact vulnerable endpoint, action, nonce failure, or fixed version. Avoid assuming exploitation paths beyond CSRF mechanics. Validation should focus on asset inventory, version confirmation, vendor advisory review, and post-update verification.

Mitigation direction

  • Inventory WordPress sites for the woolentor-addons plugin.
  • Identify any ShopLentor/WooLentor installations at version 2.6.2 or earlier.
  • Check HasThemes and Patchstack guidance for the supported fixed version.
  • Update affected plugin installations when vendor guidance confirms a safe release.
  • Limit WordPress admin access and sessions until remediation is complete.

Validation and detection

  • Confirm whether woolentor-addons is installed and active on each WordPress site.
  • Compare installed plugin versions against the affected threshold: 2.6.2 or earlier.
  • Review WordPress audit logs for unexpected ShopLentor-related setting changes.
  • Verify remediation by rechecking plugin version after update.
  • Document unaffected sites where the plugin is absent or above the affected range.
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-2022-47172 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
4.3 (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:N

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-47172Attack 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:N

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
HasThemesShopLentorwoolentor-addons, 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.