LiveActive security incident?Get immediate response
CVE Record

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

Cross-Site Request Forgery (CSRF) vulnerability in HasThemes ShopLentor plugin <= 2.5.1 leading to plugin settings change.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the WordPress ShopLentor/WooLentor plugin and can let an attacker change plugin settings by tricking a legitimate user into taking an action. The source data does not report active exploitation. Business impact is mainly site configuration tampering or disruption, not data theft.

Executive priority

Treat as a moderate WordPress application risk. Prioritize sites where the plugin controls storefront behavior or where many administrators access WordPress from email or browser sessions. This is not currently supported as an emergency exploited-in-the-wild issue by the provided sources.

Technical view

CVE-2022-46798 is a CWE-352 cross-site request forgery issue in HasThemes ShopLentor/WooLentor woolentor-addons through version 2.5.1. CVSS 3.1 is 5.4, with network access, low complexity, required user interaction, no attacker privileges, low integrity impact, low availability impact, and no confidentiality impact.

Likely exposure

WordPress sites are likely exposed only if they use the HasThemes ShopLentor/WooLentor woolentor-addons plugin at version 2.5.1 or earlier. Practical risk depends on whether an authorized WordPress user can be induced to trigger an unwanted settings change.

Exploitation context

The bundle states KEV is false and provides no evidence of active exploitation. The issue requires user interaction and is limited to plugin settings changes according to the cited description. No exploit details are provided in the source bundle.

Researcher notes

The public bundle is sparse: it names CSRF leading to plugin settings change, affected versions through 2.5.1, CVSS 5.4, and CWE-352. It does not provide a fixed version, proof of exploitation, affected settings, or exploit preconditions beyond user interaction.

Mitigation direction

  • Inventory WordPress sites for the woolentor-addons plugin.
  • Identify installs running ShopLentor/WooLentor version 2.5.1 or earlier.
  • Check Patchstack and vendor guidance for fixed versions or official mitigation.
  • Upgrade when an official fixed release is available.
  • Consider temporary plugin deactivation where exposure is material and no fix is available.

Validation and detection

  • Confirm whether woolentor-addons is installed on each WordPress site.
  • Record the installed plugin version for affected sites.
  • Review plugin settings for unexpected changes after suspicious admin activity.
  • Monitor vendor and Patchstack advisories for remediation details.
  • Verify remediation by confirming the plugin is above the affected version.
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-46798 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-2022-46798Attack 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
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.