dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-32328

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Lemmony WordPress plugin allows attackers to trick authenticated users into performing unintended actions. The attack exploits the lack of proper token validation or Origin/Referer header checks on state-changing requests within the plugin.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations and validate Origin/Referer headers on server-side to ensure requests originate from trusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Lemmony plugin is installed and get its version
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Lemmony' in the list. Note the version number displayed. Alternatively, check the file /wp-content/plugins/lemmony/ folder or examine the plugin's main PHP file for the 'Version' header in the plugin comments.
    Affected if The Lemmony plugin is installed with any version (this is a CSRF flaw affecting authenticated users of the plugin)
  2. Identify state-changing endpoints in the plugin
    Review the plugin's PHP files in /wp-content/plugins/lemmony/ for AJAX handlers (wp_ajax_* hooks), form submissions, or any functions that modify data (create, update, delete operations). Look for HTTP POST requests handling user data or site configuration.
    Affected if The plugin processes state-changing requests (any operation that modifies data, settings, or user content)
  3. Verify presence of nonce verification in state-changing code
    Search the plugin's PHP files for calls to wp_verify_nonce(), check_ajax_referer(), or wp_create_nonce(). Examine each state-changing handler identified in step 2 and confirm whether a nonce is verified before executing the action. Look for 'nonce' in form hidden fields or data attributes if accessible.
    Affected if State-changing handlers lack nonce verification (no wp_verify_nonce or check_ajax_referer calls before processing the request)
  4. Verify Origin/Referer header validation
    Search the plugin's PHP code for $_SERVER['HTTP_ORIGIN'], $_SERVER['HTTP_REFERER'] checks, or server-side validation ensuring requests come from trusted domains. Check if the plugin validates the request origin before processing state-changing operations.
    Affected if The plugin does not validate Origin or Referer headers on state-changing requests

A user is affected if the Lemmony plugin is installed and its state-changing operations lack proper anti-CSRF token validation or Origin/Referer header checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations and validate Origin/Referer headers on server-side to ensure requests originate from trusted sources.

Recommended fix Moderate confidence

1.7.1 or later

  1. Check your current Lemmony version by accessing the admin dashboard or checking the version file
  2. Backup your database and files before upgrading
  3. Download Lemmony version 1.7.1 or later from the official source (shufflehound.com or the WordPress repository)
  4. Upload and install the new version, overwriting existing files
  5. Verify the installation was successful and test that CSRF protections are functioning
  6. Clear any caches if your site uses caching
Caveat Check release notes for any breaking changes between your current version and 1.7.1

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32328 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data