LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32328: WordPress Lemmony theme < 1.7.1 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in shufflehound Lemmony lemmony allows Cross Site Request Forgery.This issue affects Lemmony: from n/a through < 1.7.1.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32328 affects the WordPress Lemmony theme before version 1.7.1. It is a CSRF flaw, meaning an attacker could trick a logged-in user into causing an unintended action. The public record rates it medium severity, with limited integrity and availability impact and no stated confidentiality impact.

Executive priority

Treat this as a routine but timely WordPress theme update. It is not currently supported as actively exploited in the provided sources, but exposed public websites should be remediated to reduce avoidable manipulation risk.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in shufflehound Lemmony for WordPress, affecting versions earlier than 1.7.1. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity impact, and low availability impact.

Likely exposure

Exposure is limited to WordPress sites using the Lemmony theme below 1.7.1. Sites not using this theme, or already on 1.7.1 or later, are not indicated as affected by the provided sources.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not listed as KEV in the supplied bundle. Practical abuse would require social engineering or otherwise causing a logged-in user to interact with attacker-controlled content.

Researcher notes

Public detail is limited. The CVE record identifies Lemmony before 1.7.1 and cites Patchstack. The affected metadata includes no CPEs and an unusual version entry, so validate exposure by installed theme name and version rather than CPE matching alone.

Mitigation direction

  • Upgrade the Lemmony WordPress theme to version 1.7.1 or later.
  • Check Patchstack and the theme vendor for any additional guidance.
  • Restrict administrative access to trusted users until affected sites are updated.
  • Use standard WordPress CSRF protections and least-privilege roles where applicable.

Validation and detection

  • Inventory WordPress sites for the Lemmony theme.
  • Confirm installed Lemmony versions are 1.7.1 or later.
  • Review administrative activity for unexpected changes during the exposure window.
  • Document remediation status for each affected WordPress instance.
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-2026-32328 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-2026-32328Attack 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
shufflehoundLemmonylemmony, 0unaffected
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.