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

CVE-2025-27355

HIGH · 7.1 CVSS v3.1 Published 2025-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Nicolas GRILLET Woocommerce – Loi Hamon loi-hamon allows Stored XSS.This issue affects Woocommerce – Loi Hamon: from n/a through <= 1.1.0.

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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'Woocommerce – Loi Hamon' (versions <= 1.1.0) allows attackers to perform unauthorized actions on behalf of an authenticated administrator, leading to Stored XSS where malicious scripts are injected into the application and executed when other users view the affected content.

MitigationImplement anti-CSRF tokens (nonces) on all forms and AJAX endpoints, add proper input validation and output escaping for user-supplied data, and update to a patched version if available from the vendor.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Verify plugin installation
    Check if the 'Woocommerce - Loi Hamon' plugin files exist in the WordPress plugins directory (wp-content/plugins/). Look for a folder named 'woocommerce-loi-hamon' or similar variant containing the plugin files.
    Affected if The plugin folder exists in the WordPress plugins directory, indicating the plugin is installed.
  2. Identify installed plugin version
    Open the main plugin PHP file (typically the primary file in the plugin folder) and locate the version declaration in the plugin header comment, or check the WordPress admin under Plugins > Installed Plugins to find the version number displayed for 'Woocommerce - Loi Hamon'.
    Affected if A version number is displayed for the plugin and it is readable.
  3. Compare version to affected range
    Compare the identified version number to the affected range. The vulnerable version range is any version <= 1.1.0.
    Affected if The installed version is 1.1.0 or lower (for example: 1.1.0, 1.0.9, 1.0.0, etc.).
  4. Confirm plugin is active
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and verify whether 'Woocommerce - Loi Hamon' shows as 'Active' rather than 'Inactive'.
    Affected if The plugin is active and running on the WordPress site.

A user is affected if the 'Woocommerce - Loi Hamon' plugin is installed, active, and running version 1.1.0 or lower, as this version range contains the CSRF vulnerability that can lead to stored XSS.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all forms and AJAX endpoints, add proper input validation and output escaping for user-supplied data, and update to a patched version if available from the vendor.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27355 — 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-2025-27355 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