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

CVE-2025-32642

CRITICAL · 10.0 CVSS v3.1 Published 2025-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This issue affects Vite Coupon: from n/a through <= 1.0.9.

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 vite-coupon plugin enables Remote Code Inclusion, allowing authenticated users to be tricked into executing malicious code through forged requests. The vulnerability affects all versions up to and including 1.0.9.

MitigationImplement anti-CSRF tokens and validation for all state-changing operations, and disable remote file inclusion capabilities in the application configuration.

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify vite-coupon plugin installation
    Search project dependencies (package.json, composer.json, or similar) and plugin directories for the vite-coupon plugin
    Affected if vite-coupon plugin is found in the project dependencies or installed modules
  2. Determine installed version
    Check the version field in package.json or the installed plugin version in node_modules/vite-coupon/package.json
    Affected if version is 1.0.9 or lower (all versions up to 1.0.9 are affected)
  3. Check for remote file inclusion capability
    Inspect plugin configuration files and source code for remote file inclusion settings, remote code execution features, or dynamic file loading mechanisms
    Affected if remote file inclusion or remote code execution features are enabled in the plugin configuration
  4. Verify anti-CSRF protection
    Review application code and plugin handlers to determine if state-changing operations (POST/PUT/DELETE requests) validate anti-CSRF tokens
    Affected if anti-CSRF tokens are NOT validated on state-changing operations in the plugin

The environment is affected if vite-coupon plugin version 1.0.9 or lower is installed AND remote file inclusion is enabled AND anti-CSRF validation is missing for plugin operations.

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 and validation for all state-changing operations, and disable remote file inclusion capabilities in the application configuration.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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