CVE-2025-30615
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Jacob Schwartz WP e-Commerce Style Email wp-e-commerce-style-email allows Code Injection.This issue affects WP e-Commerce Style Email: from n/a through <= 0.6.2.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP e-Commerce Style Email plugin allows attackers to inject malicious code through forged requests. The lack of CSRF validation combined with insufficient input sanitization enables authenticated or tricking administrators into executing arbitrary code on the affected WordPress installation.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and activation statusIn WordPress admin, go to Plugins > Installed Plugins and verify whether 'WP e-Commerce Style Email' is present and currently activatedAffected if The plugin is installed and active in WordPress
-
Identify installed plugin versionClick on the plugin name in Plugins > Installed Plugins to view the version number displayed in the plugin details, or inspect the plugin main file header using a file manager or FTPAffected if The installed version is older than the latest available version from the WordPress plugin repository
-
Review plugin admin actions for CSRF protectionInspect the plugin PHP files (typically in wp-content/plugins/wp-e-commerce-style-email/) for admin action handlers; search for presence of WordPress nonces (wp_verify_nonce, check_admin_referer) on form submissions and action hooksAffected if Plugin admin actions lack nonce verification and referer checks, meaning forms/actions are vulnerable to CSRF
-
Verify input sanitization on user-supplied dataExamine plugin code that processes user input (form fields, settings, email templates) to determine if sanitization functions (esc_html, sanitize_text_field, esc_attr) are applied before output or storageAffected if User inputs are stored or output without proper sanitization, allowing code injection
-
Confirm authenticated access to vulnerable featuresDetermine if the plugin exposes any admin pages, settings forms, or action endpoints that handle user-supplied data and are accessible to logged-in administrators or users with plugin-specific privilegesAffected if The plugin exposes settings or email template features that process unsanitized input without CSRF protection
A user is affected if the WP e-Commerce Style Email plugin is active and its admin actions lack CSRF token validation combined with insufficient input sanitization on user-supplied data fields.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of WP e-Commerce Style Email plugin if available, or disable the plugin until a patch is released. Implement WordPress nonces and CSRF tokens on all admin actions, and apply proper input sanitization/escaping on all user-supplied data.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30615 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30615 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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